This workflow is designed to support a pull-based system where tasks are processed as capacity becomes available, which helps optimize team productivity and efficiency. It's meant to simulate a physical Kanban board where the tasks in each column are marked as Blocked (or another value like Ongoing) and Ready to pull (or Done).
It's specifically intended for teams where a single task is processed by different specialists through a series of handoffs. For example, a creative team where work passes from research to design, review, approval, quality assurance, and publication.
Using this model, any task that transitions from one column to the next is immediately flagged as Blocked. This prevents people further down the production pipeline from pulling the task until it is marked as Ready to pull. These statuses are stored in a dedicated field called Kanban State
In our example, the designers are free to work on any task that the research department has marked as Ready to pull, but the reviewers are blocked from pulling the same task until the designer has finished their work.
This workflow helps you manage the Kanban state of an issue.
This workflow supports the following rules:
Block change in Kanban stage for issues that are not ready to pull
When a reported issue is moved from one stage to the next, the on-change rule in this module checks the value in the Kanban State field. If the Kanban State is not set to Ready to pull, a warning is displayed. The change is reverted.
If the Kanban State is set to Ready to pull, the Kanban State is set to Blocked when the issue is moved to the next stage.
Assign on move
This rule assigns the issue to the current user when the issue is moved, updating the value for the Stage field.