nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Average time in status diagram only shows flat line!

Sara Naddaf

hi,

we use a team-managed Jira project over a year and recently added the gadget Average time in status in the Dashboard, it is not displaying meaningful data and is instead showing a flat line with a value of zero. The scrum team also showed previously doubts about the Sprint burndown Chart reports generated in Jira, claiming it dosen't reflect the actual effort they have put in each Sprint!

Could you help me here please ?

Thank you, Sara

Accepted answers

Bill Sheboy

Hi @Sara Naddaf -- Welcome to the Atlassian Community!

Would you please post an image of what you are observing? That may provide more context.

Are you using the built in "Average Time in Status" dashboard gadget: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/

I believe that one only displays work items that have been resolved.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Sara Naddaf -- Welcome to the Atlassian Community!

Would you please post an image of what you are observing? That may provide more context.

Are you using the built in "Average Time in Status" dashboard gadget: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/

I believe that one only displays work items that have been resolved.

Kind regards,
Bill

Sara Naddaf

Hi Bill, thanks for your reply Sure I do use this same gadget, tried also to reconfigured it many times with different status been resolved, Done, Archive etc, absolutely no change results! Best, Sara

Sara Naddaf

Danut M _StonikByte_

Hi @Sara Naddaf,

That chart shows the average time spent in a status for all resolved issues over the past x days. As far as I know, it looks at the Resolution field (not at the Status) when considering an issue as resolved. So please check if your issues have the Resolution field set (not empty). This might fix.

Also, if you don't manage to figure it out, you could search for a plugin on Atlassian Marketplace that provides such gadgets.

If you consider the idea of using a plugin, our Great Gadgets app offers a Time in Status gadget that help you calculate the total or average time in each status. Also, it offers all kind of gadgets to measure cycle time and sprint or release burndown charts.

Danut.

Rahul_RVS

Hi @Sara Naddaf

If you would be interested in a mktplace app for this requirement to get the avg time in status data, you can try out

Time in Status Reports

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. You can also extract trends analysis and add that as a dashboard gadget too. The data can be exported to a CSV file too.

More details here.

Disclaimer : I am part of the app team for this add-on

TIS - Avg Time in Status.PNG

Ayça Erdem_OBSS_

Hello @Sara Naddaf

it’s a common issue, especially in team-managed projects. So, in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your need. Our app is available for both Jira Cloud, and Data Center.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee.

Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. Status Duration Report in Detail.png

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

Group By Created Month.png

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Tiimepiece reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily.

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process.

Hope it helps

Ayça

Bill Sheboy

What I meant is the "Resolved" field must have a value for the work items to display, regardless of the "Status" field value. Do your work items have a "Resolved" value?

And has the several marketplace vendors responding have indicated, the built-in gadgets and reporting are quite limited in what they provide for time-in-status reporting. When more advanced reporting is needed, marketplace apps may help.

Iryna Menzheha_SaaSJet

Hi Sara 👋

It sounds like the Average Time in Status gadget is not picking up the necessary data to generate a meaningful chart. This often happens when:

🧩 Issues don’t have enough transitions between statuses — the gadget needs that historical movement to calculate time.
📆 The date range or filter applied doesn’t include relevant issues.
🔄 There’s been a recent setup, and Jira hasn’t yet accumulated sufficient historical data.

Since you're using a team-managed project, keep in mind that some reporting features (especially historical ones) can be limited compared to company-managed projects.

If your team’s also seeing discrepancies in Sprint burndown charts, it might be worth exploring third-party add-ons, like Time in Status. To get average days aging was on a give date just

Choose Average Time Report
Sort by Project (Assignee, JQL etc)
Filter issues based on your preferred time (including issues created before add-on installation)
Access your report through Grid View

Знімок екрана 2024-09-19 о 20.53.57.png

Also you can display the average time by Chart View.

Visualize Trends

Use Time in Status reports to create exportable charts and graphs.
Add custom widgets to your Jira Dashboard for tracking metrics like average lead time or issue creation trends.

Знімок екрана 2023-12-19 о 17.19.17.png
Hope it helps

Maksym Babenko_TypeSwitch_

Hi @Sara Naddaf

I’m part of the team behind Flow Time Report, a Jira Cloud app we created to solve exactly this kind of problem.

If the “average time in status” chart is showing a flat line, it usually means it’s not capturing meaningful transitions over time. Flow Time Report displays the actual time spent in each status, directly inside the issue with clear numbers and no need for dashboards.

➡️ You can try it free: https://marketplace.atlassian.com/apps/1237782

Happy to help if you have any questions!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud