Is it possible to create JIRA reports to follow up on ticket life cycle trends?

[Silvia Saric]

Hi everyone,

There are three kinds of reports that I would like to be able to follow up on continuously in our development flow in JIRA. My question is if it is possible using some built-in or custom gadget?

1. Development Flow: How long (number of days) tickets in our Kanban board stay in each status per month: To do, Under development, Code Review, Testing, Testing on Staging, Ready for release. An alternative would be a trend of number of days in each status per month.
   
   
2. Ticket Life Cycle: How long it takes (number of days) for tickets to go from being reported to the Backlog to being resolved per month: Backlog, To do, Under development, Code Review, Testing, Testing on Staging, Ready for release, Released, Done. An alternative would be to see a trend here as well, number of days it takes for a ticket to be resolved (Released or Done) since it was reported to the Backlog.
   
   
3. Monthly Completion Trend: How many tickets get resolved per month i.e. enter status Released, Done, Closed.

Any suggestions are much appreciated. My whole point of asking this is that I want some more overviewing KPI's to start working from.

Thanks in advance!

[Mehmet A _Bloompeak_ · Accepted solution]

Hi @Silvia Saric

You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

• You can select issue fields and statuses that you want to see in your report. It 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.
• 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. It has various other reports like assignee time, status entry dates, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too.
• 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.

Here is the online demo link, you can see it in action and try without installing the app.

If you are looking for a free solution, you can try the limited version Status Time Free.

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

[Silvia Saric]

Hello @Mehmet A _Bloompeak_

This was very helpful, thank you! I just tried out the Status Time Free to begin with. I have a few questions about it: 

• Can I sort the columns in a custom order or are they always sorted A-Z? It would be nice to be able to sort according to our development workflow.

These two are the most interesting for my purpose:

• Cycle Time for Each Individual Issue:
  https://status-time.bloompeak.io/cycle-time-each-issue
• Lead Time for Each Individual Issue:
  https://status-time.bloompeak.io/lead-time-each-issue

If I understand correctly, I should create Status Groups to achieve this? Cycle Time = only statuses in our Kanban board To Do->Released, Lead Time = All statuses all together New->Released.

When I do it like that, I get a number of days even though the issue has not completed the cycle yet, is that correct? My initial assumption was that if a cycle has not been completed, then there is not summarized number of days as it is still ungoing. Currently, the Total column and Cycle Time column show the same number of days. I would assume the Total is correct, but the Cycle Time is not as it has not yet been completed in those cases.

Thanks in advance!

[Mehmet A _Bloompeak_]

Hi @Silvia Saric

Thanks for evaluating our app. You can find the answers to your questions below.

• Can I sort the columns in a custom order or are they always sorted A-Z? It would be nice to be able to sort according to our development workflow.
  -> Yes, you can. By default, status columns ordering is alphabetical but you can reorder the columns as you want as below.
  You first add the statuses that you would like to display and then you can order them using small arrows next to each as in the below screenshot.
  
• If I understand correctly, I should create Status Groups to achieve this? Cycle Time = only statuses in our Kanban board To Do->Released, Lead Time = All statuses all together New->Released.
  -> Yes, you should create status groups. For cycle time and lead time, you should not include Released status because cycle time and lead time ends when the work is finished.
• When I do it like that, I get a number of days even though the issue has not completed the cycle yet, is that correct? My initial assumption was that if a cycle has not been completed, then there is not summarized number of days as it is still ungoing. Currently, the Total column and Cycle Time column show the same number of days. I would assume the Total is correct, but the Cycle Time is not as it has not yet been completed in those cases.
  -> If you want to get cycle time of only completed issues, you can filter the issue list by choosing Status = Released as shown below.
  

Hope it helps.

[Silvia Saric]

Hello @Bloompeak Support

Thanks a lot, this is great!

I have one last question (I hope). How would you suggest I would best visualize the flow of reported tickets entering the "New" status each month? To keep track of the incoming flow of tickets. 

[Mehmet A _Bloompeak_]

Hi @Silvia Saric

You can try Jira's built-in Created vs Resolved Gadget.

If you are looking for a more advanced reporting tool, you can have a look at the article below.

How to Create Custom and Flexible Reports, Charts and Graphs in Jira

Hope it helps.

[Silvia Saric]

Hi @Mehmet A _Bloompeak_ 

I had one more question but when I went in to check the report today I got this: "Reporting is limited to 10 results because you have reached the maximum number of requests per minute. For an unlimited version please check Status Time Reports.". So I will have to get back to you on that one if we have the possibility to buy the full version.

[Mehmet A _Bloompeak_]

Hi @Silvia Saric ,

The paid version has free trial period for 1 month. You can install and try it without any payment and any limitation for 1 month.

[Silvia Saric]

For everyone else here who might be interested: Using the paid Status Time Reports, I was able to use data to create this in Excel, which is what I was aiming for report-wise. I did hope to be able to get charts like this straight into my Jira dashboard without having to use Excel, but I'm not sure if that is possible. This will do for now! Thanks for all suggestions shared here, much appreciated!

[Mariana_Pryshliak_Saasjet]

Hello @Silvia Saric 

You can try a third-party add-on - Time in Status for Jira Cloud, that includes Time in Status report and ability to track the Cycle time for each issue.

A Time in Status report shows how long an issue has been spent in each of statuses ( To do, Under development, Code Review, Testing, Testing on Staging, Ready for release). 

You can calculate the Cycle time by setting Status Groups. You can configure it from your account at the Column Manager with the drop-down list of the statuses. At the status group column, time will be summarized in accordance with custom statuses.

This add-on is developed by my SaaSJet team. so if you have any additional questions, I'm glad to help you.

[Emre Toptancı _OBSS_]

Hello @Silvia Saric ,

Let me introduce the perfect way to get the report you need, including trend analysis and charts. 

Our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center. 

Time in Status basically allows you to see how much time each issue spent on each status and on each assignee. 

   

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

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 (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

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. It supports both Company Managed and Team Managed projects.

Time in Status 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.

  

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

[Rahul_RVS]

Hi @Silvia Saric 

If you are fine with a marketplace app, you can try out our add-on to get this data

Time in Status Reports 

The main features of the app are as below

• Multiple Time in Status Reports. Excel Export available for all status reports.
  
  • Time in Status
  • Time with Assignee
  • Time in Status with Assignee
  • Time with Assignee per Status
  • Status/Assignee Count
  • Multiple Transition Reports
  • Avg Time in status reports
  • Status Transition Dates Report
  • Time in Status Per Time Grain
  • Time with Assignee Per Time Grain
• Status grouping
• Save your reports
• CSV Export
• Multiple chart types
• Dashboard Gadget

[Sudha Manneri]

New feature in JIRA- Cycle Time Report .

https://community.atlassian.com/t5/DevOps-articles/Cycle-Time-amp-Deployment-Frequency-Reports/ba-p/1780375?tempId=eyJvaWRjX2NvbnNlbnRfbGFuZ3VhZ2VfdmVyc2lvbiI6IjIuMCIsIm9pZGNfY29uc2VudF9ncmFudGVkX2F0IjoxNjQ3NTI1ODU3ODA2fQ%3D%3D