Status and workflow
How issue statuses, workflow types, and team customization work in Pulse.
Status and workflow
Status shows where an issue sits in your team's delivery process. Status drives board columns, filters, analytics, and automation.
Default statuses
Pulse ships a default workflow mapped to status types:
| Status | Status type |
|---|---|
| Backlog | Unstarted |
| Todo | Unstarted |
| In Progress | Started |
| QA | Started |
| Release | Started |
| Done | Completed |
Status types power charts and filters when you ask for "Started" or "Completed" work regardless of exact column names.
Additional types Triage and Canceled exist for filtering even when your team has no column with that name yet.
Team customization
Each team customizes workflow under:
Settings → Your teams → <team> → Issue statuses & automationsTeam managers and workspace admins can:
- Rename statuses and reorder columns
- Add or remove statuses (within type rules)
- Configure git automations and branch naming
- Set auto-close and auto-archive behavior
Changes apply to new board views immediately; existing issues keep their status until moved.
Moving issues
Change status:
- Drag cards on the board
- Use the status control on issue detail
- Bulk-update selected issues from list actions
- Apply automations when merge requests merge (when development links are configured)
Filters and analytics
Filter issues by:
- Specific status (Backlog, In Progress, …)
- Status type (Unstarted, Started, Completed, …)
Insights and dashboards group dwell time and throughput by status and type. Renaming a status does not change its type mapping.
Relations to cycles and releases
Status reflects workflow progress. Cycles and releases are separate dimensions:
- An issue can be In Progress in Cycle 12 and targeted for Release 3.2
- Completing a release usually means moving issues to Done (or your completed status)
Troubleshooting
| Situation | What to check |
|---|---|
| Missing status on board | Status may be filtered out in display options |
| Cannot drop into column | Workflow rules or permissions may block the transition |
| Status differs across teams | Each team maintains its own workflow |
Next
Last updated on