Stages and transitions
A stage (status) shows what step an object is at. The set of stages, transitions, and conditions is defined by a workflow. The page describes the workflows shipped with Assist. The administrator can change them and create their own, so the set may differ in your company: the current view is always shown in the “Workflows” section.
How to read the tables
- Key — the service name of a stage. It is visible in the audit log and in the workflow setup.
- Final — work is finished at such a stage; records at a final stage are hidden by the “Hide final stages” switch.
- Deadline (SLA) — the number of days allotted for the stage. The cabinet shows how many days remain and when the deadline is overdue. A dash means the deadline is unlimited.
- Gate — a condition without which the transition is impossible.
Task
The workflow “Task: default (seed)”, which tasks of the types Default and Bug follow. Stage names are in English because they are set in the system.
| Stage | Key | Final | Deadline |
|---|---|---|---|
| New | new | no | — |
| In Progress | in_progress | no | — |
| Review | in_review | no | — |
| Testing | test | no | — |
| Done | done | yes | — |
Allowed transitions:
| From | To | Condition |
|---|---|---|
| New | In Progress | Gate: the task must have an assignee, an estimate, a start date, and an end date |
| In Progress | Review, Testing, or Done | None |
| Review | Testing | None |
| Testing | Done | None |
| Done | In Progress | None. Returning the task to work |
After the transition New → In Progress, the assignee and the estimate are locked: a lock appears next to the fields. To change them, return the task to a stage where the fields are open, if the workflow allows it.
If a task has another type (Story, Epic, Task, your own), it may have its own workflow with its own stages. The type and the workflow are linked: a new task type automatically gets a workflow. More: “Task types”.
Release
The workflow “Release: Kanban”. More about how to close a release: “Closing a release”.
| Stage | Key | Final | Deadline |
|---|---|---|---|
| Planned | planned | no | 30 days |
| In development | in_dev | no | 30 days |
| Ready for delivery | ready | no | 30 days |
| Client acceptance | acceptance | no | 30 days |
| Closed | closed | yes | — |
Transitions go sequentially: Planned → In development → Ready for delivery → Client acceptance → Closed.
The gate of the transition “Planned → In development”. An assignee, an estimate, and a target date are needed. If something is missing, the cabinet says “Required: assignee, estimate, target date”. After the transition, these fields are locked: assignee, start date, end date, and estimate.
On the transition to the “Ready for delivery” stage, the cabinet automatically records the readiness date. The handover and client acceptance dates are filled in in the “Dates” block on the release's “Overview” tab.
Project (delivery)
The workflow “Project: delivery (system)”. It applies to projects of the type “delivery” and “product”.
| № | Stage | Key | Deadline |
|---|---|---|---|
| 1 | Idea | idea | 30 days |
| 2 | Kickoff meeting | kickoff_meeting | — |
| 3 | Proposal drafting | kp_draft | 7 days |
| 4 | Proposal sent | kp_sent | 7 days |
| 5 | Proposal agreed | kp_agreed | — |
| 6 | Development entry | dev_entry | — |
| 7 | Development | in_dev | — |
| 8 | Client acceptance | client_acceptance | 7 days |
| 9 | Financial release closing | financial_close | 7 days |
| 10 | Project completed (final) | project_done | — |
On project transitions the cabinet may check conditions and show hints: “Fill in the kickoff meeting date”, “Add the proposal file”, “Specify the current active release or create one”. The fields the hints refer to are on the project's “Overview” tab.
Project (support)
The workflow “Project: support (system)”. It applies to the support project that is created by the Create support project button after the main project is completed.
| Stage | Key | Deadline |
|---|---|---|
| Project completed | project_done | — |
| Support active | support_active | — |
| Tasks in progress | tasks_in_progress | — |
| Actual hours tally | fact_tally | 2 days |
| Documents issued | docs_issued | 7 days |
| Period closed | period_closed | — |
Hints on transitions: “An active current release is needed”, “Fill in the support end date under the contract”.
User
The workflow “User (system)”.
| Stage | Key | Meaning |
|---|---|---|
| Active | active | The person can sign in and be chosen as an assignee |
| Disabled | disabled | The person is not chosen as an assignee, past records are kept |
A transition between stages is performed in the user card with the Apply transition button.
How the cabinet reports an impossible transition
| Situation | What the cabinet shows |
|---|---|
| A gate is not met | A window or a message “Cannot move to this status” and a hint on which fields to fill in |
| The workflow has no such transition | “This status transition is not allowed.” |
| No permission to change the record | The Apply transition button is absent or inactive |
| A move is forbidden on a board | The card returns to the original column, and the reason is shown |
More: “Messages and errors”.
How to change stages
Editing is done by the administrator: “Workflows” and the process “Configuring workflows”. System workflows are cloned first, then the copy is edited.