Status Groups
Status Groups let you combine multiple workflow statuses into a single named band. Instead of seeing separate columns for "Code Review", "Peer Review", and "Awaiting Approval", you see one "Review" column showing the total time across all three.
Why Use Status Groups?
Most teams have more workflow statuses than meaningful phases. Status Groups let you map fine-grained statuses to the business concepts that actually matter - like Cycle Time and Lead Time.
Built-in Groups
Two groups come ready to use by default:
Cycle Time
Measures time from when active work started to when it completed. This is the metric your team directly controls.
Typical statuses: All "In Progress" category statuses through "Done"
Example: An issue spent 2 days In Progress, 1 day In Review, and 1 day in QA. Cycle Time = 4 days.
Lead Time
Measures total elapsed time from when the issue was created to when it was done - including waiting time before work started.
Typical statuses: All statuses from creation ("To Do") through "Done"
Example: The same issue waited 5 days in To Do before work began. Lead Time = 9 days (5 waiting + 4 active).
Creating Custom Groups
You can create your own groups to match your team's terminology.
Example: Combine "Code Review", "Peer Review", and "Awaiting Approval" into a "Review" band.
How to Set Up a Status Group
- Open the Time in Status gadget in edit mode
- Find the Status Groups section in the configuration panel
- Click + Add Group
- Enter a name (e.g., "Testing")
- Select the statuses to include (e.g., "QA", "UAT", "Regression Testing")
- Save the group
The report adds a new column showing the combined time the issue spent across all statuses in that group.
How Groups Appear in the Report
Status Groups appear as additional columns alongside individual status columns. Each group column shows the total time the issue spent across all included statuses.
You can have individual status columns AND group columns active at the same time - they do not conflict.