Workflow stages


Each board has a sequence of workflow stages that tickets move through over their life cycle. They're displayed on the board as columns of ticket cards, or as separate table sections if you're viewing the board as a list.
To get the most out of Constructor, we recommend experimenting and changing your workflow stages over time to reflect your team's work process. They're not set in stone.

Key concepts

Sequence of steps

Think of your board's workflow stages as the high-level steps a ticket should go through from inception to completion.
Generally, tickets should move through your stages forward one-at-a-time. But that's not a requirement by any means. Feel free to create stages that some tickets skip.
If you have stages that many tickets skip, consider whether it'd be clearer for your team to create an entirely separate board with its own workflow.

Stage types

When you set up your board's stages, you designate a type for each stage. A stage's type enables Constructor to present functionality for the stage only when it's appropriate.
There are three types:
  • Waiting: A holding area for tickets with no work activity. Stages with this type cannot be associated with checklists.
  • Working: A stage where some work activity is performed. Stages with this type can be associated with checklists.
  • Complete: The final stage in your board's workflow, representing work that has been completed.
Most teams' boards start with a Waiting stage with a name like To Do followed by several Working stages. However, feel free to introduce Waiting stages in the middle of your workflow.

Common patterns

There's no one best way to set up your board's workflow stages. It's a balancing act between keeping your board small and easy to scan while also modeling your team's process at a high enough resolution to be useful. We encourage you to experiment and find what works for your team. That said, here are same examples that may be helpful.

Generic workflow

To Do, In Progress, Done
If your team is new and small, this simple generic workflow isn't a bad place to begin. You can always add more stages over time as you discover the need for them.

Development workflow

To Do, Design, Development, QA, Done
Separating design, development, and testing helps make it clearer how close to completion a ticket really is. And for many teams, different people work exclusively in each of those stages, e.g., a software tester would only work on tickets in the QA stage.

"Epics" workflow

Research, Design, Development, Rollout, Impact Review, Done
Unlike development work, epics representing large features tend to have additional stages like Research, for better understanding customer problems, and Impact Review, to measure and assess how well new features are received and used by customers.


Entering stage editing mode

To edit a board's stages, visit the board, then click the ellipsis menu in the top right corner and choose Edit stages to enter stage editing mode.
While in stage editing mode, you can add a stage, reorder stages, rename a stage, delete a stage, and change a stage's type.
Anyone with access to the board can edit the board's stages. It's not restricted to users with the Admin role.

Adding a stage

Enter stage editing mode, then click the + Add stage button.

Reordering stages

Enter stage editing mode, then drag and drop a stage to change the order.
The final stage in your board's workflow must have the Complete type. If you move a column to the end, its type will automatically change to Complete.

Changing a stage's type

Enter stage editing mode, then choose a type from the stage's dropdown menu.

Deleting a stage

Enter stage editing mode, then choose Delete stage from the stage's dropdown menu.
Only empty stages can be deleted.
Constructor doesn't support hiding a stage from view. If you feel tempted to hide a stage, consider just deleting it and using lightweight assignable discussion threads to model it instead.