Match issue types and statuses to the work
An issue type describes what the work is; its status describes where it is in the process. Build a valid hierarchy, add the columns your project needs and verify the transitions that connect them before moving real work through the board.
Boards → Kanban board options → Manage workflowWhat you’ll learn
- Choose among five issue types.
- Create valid parent and child relationships.
- Test statuses and permitted transitions.
Captured in Boilerrum with an illustrative project. The app interface is shown in English.
In this guide
01
Choose the type for its purpose
Open Details and inspect Type. Epic represents a broader outcome, Story a meaningful slice, Task an action, Sub-task a smaller action under a task, and Bug a problem to resolve. Use Priority separately to express urgency. After changing a type, check for validation errors: the issue’s existing parent and children still need to form a valid hierarchy.
02
Build only compatible parent relationships
In Roadmap, use a row’s Add menu or Add child issue control to see the allowed children. An Epic can contain Stories, Tasks and Bugs; a Story can contain Tasks and Bugs; a Task can contain Sub-tasks. Bugs and Sub-tasks have no children. Use Parent issue in Details to change a compatible parent and verify the resulting tree.
03
Inspect the project’s existing statuses
Open Boards and compare column titles with Status in an issue’s Details. Columns correspond to workflow statuses, while categories express a broader stage such as waiting, in progress or done. A display name alone does not define a permitted move. Use a small sample issue to establish which existing columns and transitions already match your process.
04
Add a status through a board column
Select Add column on the board. Enter New column title and choose Category before selecting Create. This adds the status to the active workflow and a corresponding column to the board. Use a clear stage name such as Review. Inspect the new column and its category, then use Column options if the title needs correction.
05
Connect the permitted status transitions
Open Kanban board options and choose Manage workflow. Inspect the diagram’s status nodes and directional connections. Drag between status handles to create the needed transition; select an unwanted connection and delete it while the diagram has focus. Use Save when finished. Reopen the editor to verify the actual graph before treating the new path as available.
06
Test the process with an issue
Move your sample card through the intended columns, then inspect Status in Details after each move. A rejected transition should leave the issue in its previous state and provide feedback. Verify completion against the workflow’s done or terminal status, because sprint completion uses that meaning. Reopen Manage workflow to confirm the tested path; this project’s workflow is saved in this browser.
A valid issue hierarchy and a tested project workflow whose column moves reflect meaningful progress.