What is the average time your team spent to finish the project? Or how long does it take an assignee to complete a task on average? Let’s figure out what average metrics you can use in Jira.
With built-in Jira functionality, you can find some gadgets to count average metrics on the dashboard. Use the “Add gadget” button in the dashboard menu.
This bar chart shows the average number of days issues were unresolved. It will help if you need to see a general picture for some project or filter. The list of issues is taken from the number of days you select starting from today. It can be 5, 10, 30, 50, or any other number you type.
How to configure
As a result, you’ve got a graph like on the screen below:
The average is calculated by dividing the total time by the total number of issues recorded per period.
This chart shows the average time spent in chosen status for all resolved issues for some period.
How to configure
The gadget shows only time in status for resolved issues. Also, users face a problem of inaccurate results when the chart returns the issues that were not in the resolved state. Read more here.
To enhance Jira Cloud in quick orientation in time reports, our SaaSJet team has developed such a plugin as Time in Status for Jira Cloud. It works for Jira`s classic and next-gen projects. You can find the average time in status for project, assignee, sprint, etc. Average cycle time and lead time are also configurable.
All of the reports can be displayed on Jira dashboard as gadgets.
This report shows the average time spent in particular status for each day of the sprint. If you choose another filter like a project, epic, or label, then you can set any date range you need.
To get the helicopter perspective on average time in Jira status, try to view this report as a chart.
How long does it take on average for your team members to complete a task or project? This report will help you to find out. You can select any dates for the time reporting period.
Average cycle time counts the time an issue is marked as “in progress”. For example, it may include “in progress” and “to review” statuses depending on the workflow you use. If you’d like to read more about the cycle and lead time, check out the article with a pizza example.
To get an average cycle and lead time using the status group option.
What tools do use to find mean resolution time for your team? Please share any solutions and advice on the average time spent to make the most out of Jira. You are welcome to try the ones described in the article.