Atlassian analytics - TIme in Status

[Jstenger]

Using Analytics, I am working on time in status template dashboard and charts. 

Does anyone have any experience with the setup for this? 

Questions:

Any suggestions for better filters? (Screenshot #1)

On the charts, I am not exactly sure what "average time in status (days)" means as it relates to this chart. (Screenshot #2)

Not sure what the pink line on the top represents. (Screenshot #2)

Not sure what the numbers represent for pending, open, In Progress or work in progress. Is it counting Days? (Screenshot #3)

Thank you in advance for any guidance you can provide. 

[Gizem Gökçe (OBSS)]

Hello @Jstenger ,

Welcome to the community!

"Average Time in Status (days)" represents the average duration issues spend in a specific status. The pink line could indicate trends or benchmarks for a particular status, as shown in the chart legend. If you're looking for more advanced and precise reporting, I recommend exploring Timepiece - Time in Status for Jira, developed by our team at OBSS, we specialize in tracking time spent in statuses and providing actionable insights through customizable reports and dashboards. While Atlassian Analytics itself doesn’t natively provide all the features for detailed Time in Status tracking, our app offers seamless solutions tailored for such use cases. 

With Timepiece: Using the Status Duration Report, you can filter and group data by key fields like Created Month/Year, Assignee, or Issue Type. This makes it easy to zoom in on the exact data you need for meaningful insights. Below, I’ve included an example screenshot:

1. Grouped by Created Month and Year: Displays average time spent in each status over time, allowing you to identify trends and bottlenecks. 

2. Visual Chart: A clean, interactive chart generated from the report, showing trends and averages at a glance. 

Timepiece - Time in Status for Jira is easy to set up and integrate with your workflows. You can try it directly from the Atlassian Marketplace, and our team is available to help with any questions you may have. 

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features. 

Hope it helps,

Gizem

[Ayça Erdem_OBSS_]

additonally i would like to add 

[Danut M [StonikByte]]

Hi @Jstenger,

The pink line represents the average time the issues from your filter spent in certain status. To identify the status, look at the chart legend to see which status is associated to the pink line. In your case the pink like represents the "Work in Progress" status. 

The numbers represent days, in your example, the issues spent as average 415.05 days in Work in Progress status.  

I'm afraid that these charts do not help to identify the status for individual issues; they just display the data overall (for all the issues in filter).

If these charts are not useful for you, an alternative solution would be to search for a plugin on Atlassian Marketplace that offers Time in Status tracking / reports.

In case you want to try a plugin, our Great Gadgets app offers a Time in Status gadget that also display a Data tab with individual issue and their time in status.

See also this article explaining this gadget in the context of Jira Service Management: https://community.atlassian.com/t5/App-Central-articles/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369

Danut.  

[Sahir Maharaj]

Hello @Jstenger

From my experience, "Average Time in Status (days)" represents the average duration issues spend in a specific status.

The pink line could indicate benchmarks or trends based on historical data. Ensure you configure filters to reflect relevant workflows and validate the chart settings.

[Jstenger]

should that number change as the number of days change in the calendar filter?

for example: If I am filtering for this time then should the numbers say 0-30 (respectively) not 0-400? (see screenshot as example).

I am looking for a way to show how long a ticket was in each status.