Report Types
StatusPath Reports currently exposes six report types in the main report selector: Time in Status, Average Time in Status, Time in Assignee, Status Count, Status Entry Date, and Transition Count.
Choose the report type based on the question you need to answer, then choose the scope that contains the right work items.
When to use this
Use this page when deciding which report type to run or when explaining the meaning of a report result.
Before you begin
- Identify the workflow question you are trying to answer.
- Choose the Jira work items you want to analyze.
- Confirm whether you need issue-level rows, averages, dates, or counts.
Steps
- Open StatusPath Reports.
- Choose the report scope.
- Select a report type.
- Apply status, field, and time settings if needed.
- Run the report.
- Review the table, chart, or export.
Report type reference
Time in Status
Purpose: Shows how long each work item stayed in each selected status.
How to read it: Each row is an issue. Status columns show duration values for that issue.
Best for: Finding bottleneck issues, review delays, waiting time, and cycle time details.
Notes: The report builds a status timeline from the created date, status changelog events, optional Trim History boundaries, and the report generation time. If a work item entered the same status multiple times, the duration cell accumulates those segments and stores an entry count.
Average Time in Status
Purpose: Calculates average time spent in statuses across selected work items.
How to read it: Use averages to compare workflow stages across a project, sprint, filter, or query.
Best for: Team reviews, management summaries, and trend comparisons.
Notes: The report starts from Time in Status row data and aggregates average durations by selected Group By dimensions such as time buckets, project, issue type, current status, assignee, reporter, priority, resolution, and parent where available.
Time in Assignee
Purpose: Shows how long work items were assigned to users.
How to read it: Assignee columns or groups show duration by person.
Best for: Understanding ownership time, handoffs, and waiting time by assignee.
Notes: The report uses assignee changelog events. If an issue is unassigned for part of its history, the report keeps Unassigned as its own duration column.
Status Count
Purpose: Counts how many times work items entered selected statuses.
How to read it: Higher counts can indicate repeated review loops, rework, or workflow churn.
Best for: Detecting rework and noisy transitions.
Notes: Status Count uses the same status timeline foundation as Time in Status, but displays entry counts instead of duration values. Duration format and work schedule controls are not shown because the output is counts.
Status Entry Date
Purpose: Shows when an issue entered a selected status.
How to read it: Use the date to understand when work reached a workflow stage.
Best for: Audits, handoff checks, and aging reviews.
Notes: The report formats the first entry date for each visible status column. If a work item never entered a status, the cell is blank or a dash in the table/export output.
Transition Count
Purpose: Counts workflow transitions for each work item.
How to read it: A high transition count may indicate rework or a complex workflow path.
Best for: Workflow cleanup and process improvement.
Notes: Transition Count reads status changelog events and creates transition columns for source-to-target pairs such as To Do -> In Progress. The output is counts, not time durations.
Cycle Time and Lead Time exist in calculation and saved-report restore compatibility code, but they are not shown as regular V1 report choices in the current report selector.
Result
You should see a table or chart that matches the selected metric. Exported files include the selected report columns and calculated values.
Troubleshooting
If a report type does not answer your question, switch to a metric closer to the workflow behavior you want to inspect. For example, use Status Count for repeated entries and Time in Status for waiting time.