## Workflows

A workflow defines the path of issue resolution — from acceptance to closure. It consists of statuses, steps, and operations between them.

Management is available under **Configuration → Workflows**.

## Workflow diagram

![Workflow diagram](/rkl-workflow-diagram-en.jpg)

The diagram visualises steps and connections between them. It is generated from the current configuration and updates after every change.

## Statuses

Statuses are a dictionary of states defined at the workflow level. Each status has a multilingual name, a colour, and an active flag. Each workflow step is assigned **one** status from this dictionary.

Statuses are managed from the workflow page under **Workflow statuses**.

## Steps

A step represents a phase of issue resolution (e.g. *Received*, *In progress*, *Closed*). Each step has:

- **Name and description** — multilingual
- **Status** — one status assigned from the workflow's status pool
- **Colour** — highlight colour shown on the issue list
- **Starting step** — marks the step where new issues are created
- **Final step** — marks the step where issues are closed
- **Maximum duration** — how many working days an issue may remain in this step (0 = monitoring off)
- **Permission groups** — which groups have access to issues in this step

Steps are managed from the workflow page under **Workflow steps**.

## Operations

An operation is an action that moves an issue from its current step to another. Operations are assigned to a specific (source) step. Each operation has:

- **Name and description** — multilingual; the name is displayed as a button on the issue details page
- **Target step** — which step the operation moves the issue to
- **Display order** — the order of operation buttons on the issue details page
- **Permission groups** — which groups can execute this operation

Operations are managed from the step page under **Step operations**.

## Step and operation permissions

Permission groups can be assigned independently to steps and to operations:

- **Step permissions** — define which groups can see and access issues in that step
- **Operation permissions** — define which groups can execute the operation (move the issue to the next step)

---

## FAQ

### Can one workflow be used by multiple issue types?
Yes. The same workflow can be assigned to multiple issue types.

### What is the difference between a step and a status?
A step is the main phase of issue resolution (e.g. *In progress*). A status is a state label assigned to a step (e.g. *Open*). Each step has exactly one status.

### What is an operation?
An operation is a button on the issue details page that moves the issue to another step. It is assigned to a source step and points to a target step.

### Can access to a step be restricted?
Yes. Each step has assigned permission groups — only users belonging to those groups have access to issues in that step.

### Can access to an operation be restricted?
Yes. Each operation has assigned permission groups — only users in those groups can see and click the operation button on the issue details page.

### How many workflows can I create?
The number of available workflows depends on the selected subscription plan.

### Can I delete a step that has assigned issues?
No. A step can only be deleted if no active issues are in that step.