Reports of Time in Status for Jira Data Center

With Time in Status for Jira you can generate 7 types of reports:

1. Time in Status report - contains columns with information about issues (Type, Key, Summary - are constant; Assignee, Status) and columns with time in status of every issue + Total time of task.

Open

2. Average Time report shows the average time spent in status.

Open

The picture shows the logic of calculating the Average time.

1. We count the number of tasks that have been in a particular status (To-Do status in this case) (green line),

2. Then, sum the time of these tasks (blue line). We take into account only those tasks that have been in the status.

3. Divide the total time by the number of tasks. (1/2)

This is how the calculation of each value on the grid is occurring. 

3. Status Count report displays how often an issue has been in a particular status during the chosen period.

4. Time in Status per Date report sums the time an issue has been in a particular status during the chosen period.

5. Assignee Time. The report provides insights into how much time an issue has spent in each status while assigned to a specific user or assignee.

It helps to find answers to such essential questions as:

• Which status consumes the most time for assigned issues?

• Are there any recurring patterns in the time spent in specific statuses?

• Which assignees are most efficient in handling tasks?

6. Transition Count report indicates the frequency with which an issue transitions across various statuses within the workflow.

Users can identify critical stages in the workflow where issues undergo frequent changes, indicating areas that may require closer attention or optimization. Understanding patterns in transition counts can help identify common issues or challenges in the workflow process that may require further investigation or improvement.

7. Status Entrance Date report in Jira provides insights into when an issue entered a particular status within the workflow. It is a history of status changes for tasks with specific dates. 

This allows the user to understand when exactly the status change occurred since Jira does not provide such information.

The report is mainly intended to understand the life cycle of an issue.