...
Combine with filters like issue type, labels, or changelog assignee for focused insights.
Save the report and configure recurring views to track improvements.
Use conditional formatting to highlight rows, columns, or specific values
Export to Excel or PDF to share results with stakeholders.
...
Other useful measures to customise the report
Note: Combine these measures with “Changelog status“ or “Changelog assignee“ fields to get the data for all historical statuses and assignees.
🕓 Time in Status
Description:
Calculates the total time an issue spent in each Jira status. It aggregates durations between status transitions based on the issue's changelog. This helps identify where work gets delayed or blocked.
Example Use Case:
See how long issues remain “In Progress” before completion.
👤 Time in Assignee
Description:
Calculates the total time an issue was assigned to each user throughout its lifecycle. This is based on the issue’s assignee change history (changelog).
Example Use Case:
Understand workload distribution by measuring how long each team member held issues.
...
🔁 Count of Status Occurrences
...
Example Use Case:
Find issues that were reopened multiple times or bounced between “In Review” and “In Progress”.
...
📆 First/Last Entered or Exited Status
...
Example Use Case:
Find when a ticket first entered “Waiting for Support” or when it last exited “Backlog”.
...
...
🕒 Time in Status 24/5
Description:
Calculates time spent in status, assuming 24 hours per day, 5 working days per week (Monday to Friday). Ignores weekends and outside working days, making it more business-context accurate.
...