How can I set up a Jira dashboard that shows cycle time for all Stories and tasks in a sprint
Asked by Graeme Doyle:

How can I set up a Jira dashboard that shows cycle time for all Stories and tasks in a sprint? The team is having a terrible time with Stories taken too long and spilling into next sprint. I want to run a retrospective but I need to show then cycle times per issue type. Any help would be fantastic.


Answers:
author: Valeriia_Havrylenko_SaaSJet
body: Hi [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512) ?  
Welcome to the Community!  

If you consider installing third-party add-ons, option for you can be [Time in Status](https://marketplace.atlassian.com/apps/1219732/time-in-status-for-jira-cloud?hosting=datacenter&tab=overview&utm_medium=referral&utm_campaign=Comment_How-can-I-set-up-a-Jira-dashboard-that-shows-cycle-time-for-all_20240912). You can get various real time reports with add-on. To get cycle time (total duration) just choose right statuses for calculation and you will be all set!

![?????? ?????? 2024-09-12 ? 21.08.10.png](https://community.atlassian.com/t5/image/serverpage/image-id/347196iBC81ED97865C9839/image-size/large?v=v2&px=999 "?????? ?????? 2024-09-12 ? 21.08.10.png")

Add-on developed by my team. You can also [book a live demo](https://calendly.com/vitalii_meeting/time-in-status?utm_source=Atlassian_Marketplace&utm_medium=referral&utm_campaign=Button_more-info) - we'll show you the application inside out and answer all your questions.  

I hope this helps ?


author: Gizem G?k?e _OBSS_
body: Hello [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512) ,

For your needs, I can recommend [Timepiece (formerly Time in Status)](https://marketplace.atlassian.com/apps/1211756/) , the oldest and the most comprehensive "Time in Status" solution in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Data Center and Cloud.

Timepiece mainly allows you to see how much time each issue spent on each **status** or each **assignee** . You can combine the time for multiple statuses to get metrics like **Issue Age, Cycle Time, Lead Time, Resolution Time** etc.

You can easily use your predefined **sprints** as filter type and you can create reports calculated specially for your sprints.

![4.png](https://community.atlassian.com/t5/image/serverpage/image-id/346534i828991B2CFC0F466/image-size/large?v=v2&px=999 "4.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 cycle time per *scrum team*or average resolution time per issue type.

![3.png](https://community.atlassian.com/t5/image/serverpage/image-id/346533i81667BA1F2CE753F/image-size/large?v=v2&px=999 "3.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.

Timepiece 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.

![Dashboard View.png](https://community.atlassian.com/t5/image/serverpage/image-id/346535i63F40EEAA4F44A36/image-size/large?v=v2&px=999 "Dashboard View.png")

Visit [Timepiece (formerly Time in Status)](https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud&tab=overview&utm_source=community&utm_medium=answer) to experience the full range of features.

If you wish, you can also [schedule a live demo.](https://calendar.app.google/faQYgsEekRdFxnPj7) We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem


author: Madhu_RVS
body: Hi [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512)

You can use Jira Rest API's to pull this data from issue changelogs. Or You can create your own custom fields and apply [Jira automation](https://www.atlassian.com/software/jira/features/automation) to populate those.

Alternatively if you are open to try a mktplace app, pls do take a look at

[Time in Status Reports](https://marketplace.atlassian.com/apps/1226187/time-in-status-reports?hosting=cloud&tab=overview)

With this app you generate time in status for multiple issues with multiple filter and grouping options. You can also group your statuses to define you cycle times. The app can easily be added as a dashboard gadget.

[More details here.](https://community.atlassian.com/t5/App-Central-articles/Reports-to-extract-Time-in-Status-data/ba-p/2348133)

Disclaimer : I work for the vendor who built this app

![TIS - Cycle Time report.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/346093i4EE42F2FB3B572FF/image-size/large?v=v2&px=999 "TIS - Cycle Time report.PNG")


author: Hannes Obweger - JXL for Jira
body: Hi [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512)

welcome to the community!

As you can see from the previous answers, this is an area where many Jira users rely on apps from the Atlassian Marketplace to fulfil their reporting needs.

If a Marketplace app is an option for you, I think you might like the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=datacenter&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2805766).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you'd do in e.g. Excel or Google Sheets. It also comes with a number of so-called *history columns* that aren't natively available, including an issue's *time between created and resolved* , *time in \[status\], or time between \[status\] and \[status\].*

This is how it looks in action:

![time-in-status.gif](https://community.atlassian.com/t5/image/serverpage/image-id/340525i917C566CC2D872B7/image-size/large?v=v2&px=999 "time-in-status.gif")

As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) *issue hierarchies* , *issue grouping* by any issue field(s), *sum-ups* , or *conditional formatting*.

As every JXL sheet is powered by a JQL statement, you have full control over which issues you want to see in your sheet.

Any questions just let me know,

Best,

Hannes


author: Josh Costella
body: Hi [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512)

Apologies that you are getting spammed with nothing but plugin recommendations.

From a process perspective, I don't think cycle time is the right thing to measure for your use case. If you are doing sprints, the cycle time is the length of the sprint. The stories are either complete or they're not.

The type of report you are asking for doesn't tell you the root cause. Your sprint reports in your board give you a breakdown of everything that was complete, incomplete, added, and removed during the sprint. From there, you can start to investigate.

I would interview the team/assignee, ask why they couldn't get the story complete for the sprint. Is the team taking too much on? Are you using story points or hours as an estimate? Are stories getting added mid-sprint? Is the team working on items outside of the sprint? Are the stories not defined well enough with clear deliverables? These are all questions that need to have answers in order to get to the root cause of why the team is rolling stories to additional sprints.


author: Danut M _StonikByte_
body: Hi [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512),

Jira does not offer a cycle time gadget. But you can visualize the cycle time for the issues in your sprint by using the **Control Chart report** available in your Scrum board.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/346094i4261CAE7334E388A/image-size/large?v=v2&px=999 "image.png")

Unfortunately this report does not offer a data table, so you will have to hover each issue in the chart to visualize the cycle time in the tool-tip.

If you want something better, you should search for available app on Atlassian Marketplace.

If you consider the idea of using an app, our [Great Gadgets](https://marketplace.atlassian.com/search?query=stonikbyte%20great%20gadgets%20agile) app offers many gadgets that allow you to measure the **cycle time** or **time-in-status** for the issues in your sprint. See for example, the **Control Chart gadget**:

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/346095iB1052D6F14BB8DDA/image-size/large?v=v2&px=999 "image.png")

It has the advantage of showing a Data tab with all the issues and their cycle time, which you can export in CSV and discuss it further with the team in the retrospective meeting.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/346096i55AAC9CB1D71C898/image-size/large?v=v2&px=999 "image.png")

Hope this helps.

Danut.


author: Mehmet A _Bloompeak_
body: Hi [@Graeme Doyle](/t5/user/viewprofilepage/user-id/5571512)

If you prefer to use a marketplace app, you can try [Status Time Reports](https://marketplace.atlassian.com/1221826) app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

You can use**cycle time** (the time it takes for the team to start working on an issue and complete it) or **lead** **time** (the time interval between the moment an issue is requested to the moment it is completed) **reports to monitor the productivity of the team, analyze and understand the dynamics behind it and take necessary actions** . Here is the [online demo link](http://status-time.bloompeak.io/demo), you can see it in action and try without installing the app. For your case, you can have a look at [Cycle Time for Each Issue](https://bloompeak.atlassian.net/plugins/servlet/ac/io.bloompeak.status-time/st-report?ac.reportid=901) and [Lead Time for Each Issue](https://bloompeak.atlassian.net/plugins/servlet/ac/io.bloompeak.status-time/st-report?ac.reportid=904) reports.

For further details, you can have a look at [Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters](https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Cycle-Time-and-Lead-Time-in-Jira-Productivity-Measurement-with/ba-p/1905845) article and [Status Time Reports How to Videos.](https://www.youtube.com/playlist?list=PLVHoaAkoFPJnG9nLkzcxG0P00ndQgimDs)

++App Features:++

* This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

* You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
* Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
* You can set different duration formats.
* You can export reports in CSV file format and open them in MS Excel.
* You can also add this app as a gadget to your Jira dashboards and reach "Status Time" from Issue Detail page.
* You can enable/disable access to Status Time reports\&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely **free** solution, you can try the limited version [Status Time Reports Free](https://marketplace.atlassian.com/apps/1222051).

If you have any questions, feel free to [schedule a demo](https://bloompeak.io/schedule-a-call) with us.

Hope it helps.


Tags: data-center

jira-data-center