Status transition history
Status transition history
CLOUD
The Status transition history panel gives you a structured view of how a work item moved through the workflow - every status change, who made it, when, and how long the issue stayed in each status.
This is useful when you need to:
Understand why a ticket took longer than expected
Identify handoff delays or repeated back-and-forth between statuses
Check how long a ticket spent in a specific stage
See who moved the ticket and when
Accessing the panel
The Status transition history tab is available in the Activity section of the issue layout.
In the example above, you can see that the ticket passed through several stages handled by two team members. A few things stand out:
The ticket spent 2 weeks 4 days in In Code Review - significantly longer than the other stages
Testing was not completed on the first attempt: the ticket moved from In Testing back to Ready for Test on June 2, then re-entered In Testing the same day, adding an extra 1 day 2 hours of rework
The Time in status of
0on the third row reflects that the ticket left In Testing immediately - it was sent back for fixes without any delay
Table columns
Column | Description |
|---|---|
Transition from status | The status the issue was in before the transition |
→ To | The status it moved into |
When | Date and time of the transition (sortable) |
By | The user who made the transition (sortable) |
Time in status | How long the issue spent in the From status for that specific entry (sortable) |
Each transition appears as a separate row. If an issue moved through the same status multiple times, each visit is shown individually - the Time in status column reflects that single visit, not the cumulative time across all visits.