Calculating a ticket Cycle time

[ori gal]

Hello,

I would like to build an automation that will calculate the number of days a ticket spends between "In Progress" to "Done" and write it to a custom field I created on the ticket.

The trigger part is easy (ticket transition from "to do" to "in progress").

How do I set the rule that calculates the time betwee the statuese ("In Progress" to "Done")? 

Thanks!

[Emre Toptancı _OBSS_]

Hello @ori gal

You can do this with automation but you will need to create a custom field and an automation for each status time you want to measure. It will be expensive to build and maintain. Additionally, if you try to do this for a lot of measurements, those custom fields will put a lot of pressure on your Jira.

On the other hand, the data needed for this information is available in each issue's history but Jira does not give this as a ready-to-use report. I suggest you use a marketplace app for this. It will be faster and overall cheaper.

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center.  

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

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. 

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 for Jira Cloud.

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.

   

Timepiece - Time in Status for Jira

EmreT

[ori gal]

Hi Emre, and thank you for your response.

I'm familiar with Time in Status and have worked with it in the past. It's great to get general stats on the cycle time and avg. Time in status; however, Im would like to see the Number of days (cycle time) on the ticket itself and compare it to the cost estimation.

I don't believe that this app is the solution I'm looking for.

Thanks!

[Iryna Komarnitska_SaaSJet_]

Hi @ori gal ,

Try using the Time Between Statuses app from my team.  

You create a Cycle Time status, and the app automatically generates a report for you and counts the time spent in the statuses.

For further calculations, you can easily export the report in a convenient format.

I hope you find it useful. Please contact me if you have any questions; I will happily answer them.

[Mehmet A _Bloompeak_]

Hi @ori gal

If you prefer to use a marketplace app, 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.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Time in Status for Each Issue report. For further details, please see Status Time Reports How to Videos.

• 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, 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 Free.

Hope it helps.

[Chris Boys]

Hi @ori gal 

I can't answer your question upfront on how to how to set the rule, but I was interested in your primary question of how to compare actual days spent on the ticket relative to the cost estimation. 

Umano has a possible lens on that for you in its Capacity metric.

For the assigned tickets in a sprint, this snapshot shows the estimated (planned) capacity allocated to each ticket in Story Points (also displayed in days, calculated as the usual cycle time for that team for that estimate size).

For this team, a ticket sized 3 SPs takes them 5 days  - that's your budget, and what 100% is for that ticket.

If more than 5 days is spent on that ticket (unplanned capacity in blue), you're over budget, and effectively borrowing from 'available' capacity from tickets you haven't yet started. In the example below, in the bottom ticket, you've spent an additional 4 days, or 81% more than budgeted.

Just offering another possible way you can answer the question without building your own solution.  

Let me know if I can help as I'd be happy to share more.
Chris / Umano

[ori gal]

Hi Chris,

Your solution seems interesting, however, I don't think it will work for 2 reasons. I'm looking for a plan vs. actual on the item level (not sprint / team) and the cost is high while I have no budget. 

Thanks! 

[Chris Boys]

Hi @OriO, just for clarification, the above is calculating planned vs actual (you can see the ticket number/issue key per item above) per item; we just so happen to also provide this at the team/sprint level.  Also, we have a freemium version available.  Let me know if you can help you get to your insights any sooner.  Cheers, Chris 

[OriO]

Hi @Chris Boys 

I think you mistagged Ori Gal user. 

Let's hope @ori gal got the notification in time ;)