Workflow overview
Your project's workflow is the set of statuses an issue can be in, plus the rules for moving between them. It's what turns "someone should fix that" into a process everyone follows the same way.
The five status types
Every status in Builddar is one of five types. The type decides the status's behavior; the name is yours to change.
| Type | Role in the flow |
|---|---|
| Open | Where new issues start. Exactly one per project. |
| In Progress | Work is happening. You can add several of these. |
| Completed | The assignee says the work is done. |
| Validated | Someone checked the work and accepted it. |
| Rejected | The work was checked and refused — it goes back. |
A typical project runs Open → In Progress → Completed → Validated, with Rejected as the loop back when a check fails.
Open, Completed, Validated, and Rejected are system-defined: you can rename and recolor them, but you can't create more of them or delete them. The statuses you add are always of type In Progress. A project holds at most 8 statuses.
Transitions
A transition is a permitted move from one status to another — for example In Progress → Completed. If there's no transition between two statuses, nobody can make that move.
Each transition can carry conditions:
- Requires a comment — the person must explain the change.
- Requires an attachment — the issue must have a photo or file on it.
- Requires date fields — certain dates must be filled in, for example the completion date.
- Allowed roles — which project roles may perform it: Manager, Collaborator, Guest.
This is where authorization actually lives. Letting a subcontractor mark work Completed but not Validated is a transition rule, not a role setting.
Give Completed → Validated to Managers only, and Open → Completed to Collaborators and Guests. The contractor reports their work as done; your team decides whether it is.
Status history
Every status change is recorded on the issue: which status it came from, which it went to, who changed it, when, and the comment they left. Open an issue's status history to see the full chain.
Who can change the workflow
Required role: Project Manager (or Organization Admin).
Customizing statuses and transitions depends on your plan. Without it, your project uses the standard workflow — which still works fully, you just can't change it.
Each project has its own workflow. Changing one project's statuses never affects another.
Guides in this section
See also Update an issue's status.