Jira admins
Validate app access, saved report behavior, scopes, permissions, and reporting defaults.
StatusPath Reports
Jira Time in Status Report with Status History
In Report Center, analyze how long Jira work items spend in each status, open an Average Work item count, review its contributing work items, and continue to one work item’s Journey.
New in 2.5: Report Center connects an Average Work item count to its contributors and then to an individual work item Journey.
Who it is for
Built for teams responsible for Jira delivery flow.
Scrum masters
Prepare sprint retrospectives with evidence about waiting time and repeated workflow movement.
Delivery managers
Compare workflow delays by status, project, priority, assignee, and reporting period.
Support and operations teams
Review queue aging, blocked time, ownership handoffs, and exportable weekly reporting views.
Use cases
Built for common Jira workflow questions
Start from the question your team needs to answer, then choose the report type, Jira scope, table, chart, saved setup, or export that fits.
Which issues spent the longest time in review?
Sort duration columns to find the exact work items that waited the longest.
Where are blockers accumulating?
Compare status totals and averages to see where work is slowing down.
Which assignees or handoffs slow down delivery?
Review Time in Assignee and ownership patterns across the selected scope.
How often do issues re-enter the same status?
Use Status Count and Transition Count to surface repeated-movement signals, then apply your team’s rework definition and verify the underlying work items.
What changed across sprints, epics, or saved filters?
Start from the Jira scope your team already uses and compare repeatable views.
Which reports should be exported for retrospectives or audits?
Save recurring setups and export CSV/XLSX files with the current report evidence.
Main capabilities
Why StatusPath Reports?
The product combines scope, table, chart, saved report, and export workflows without turning every report into a custom dashboard project.
Find bottlenecks fast
Sort by status duration, compare averages, and identify where work items wait the longest.
Report from the Jira scope you already use
Start from Project, Filter, JQL, Sprint, or Epic without rebuilding your Jira reporting setup.
Analyze status, assignee, and transition patterns
Review Time in Status, Time in Assignee, Status Count, Status Entry Date, and Transition Count in one focused reporting experience.
Export and reuse your reports
Save recurring report setups and export CSV/XLSX files for reviews, audits, and stakeholder updates.
Reports
Core report types
Start from a practical reporting question, then switch between table and chart views as needed.
Time in Status
Measure total time each work item spends in selected workflow statuses.
Average Time in Status
Compare average status duration across a selected group of work items.
Time in Assignee
Understand how long issues are assigned to each person during the selected period.
Status Count
Count how many times work items entered selected statuses.
Status Entry Date
Show when each work item first entered key statuses in the calculated history window.
Transition Count
Count status transitions to surface review-loop or workflow-noise signals for manual verification.
See the Jira Average Time in Status formula and worked example
Scope
Choose the work items you want to analyze.
Choose the Jira work items you want to analyze using flexible report scopes. Scope controls the dataset before StatusPath Reports calculates duration, count, and trend metrics.
- Project
- Filter
- JQL
- Sprint
- Epic
Table reports
- AG Grid report view
- Dynamic status columns
- Issue field columns
- Status groups
- Assignee groups
- Duration sorting
- Duration filtering
- Native table filtering
Charts
- Top Bottleneck Issues
- Status Trend
- Cross-report trend charts
- Chart export
Time settings
- Date range
- Duration formats
- Business calendar
- Business hours
Trust
Learn more about security and data handlingBuilt for Jira Cloud teams.
Uses Jira permissions
Focused on reporting configuration, not frozen report-row storage
Supports saved setups and export workflows
Built for Jira Cloud teams
Open the work items behind a Report Center average.
Run Average Time in Status from a real Jira scope, open a Work item count, then inspect a contributing work item’s Journey when the result needs an explanation.