You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Checking to see if there is a gadget in Jira Cloud compatible to Cycle Time Trend Gadget from Jira Sever/Data Center. If not is there a JQL I can use to get the same results in a Dashboard.
You should populate 2 custom fields. One for storing the progress start time and one for the storing the cycle time.
Now all the done issues will have a CycleTime field populated.
Thank you for the update. We need a report that will tell the user a start and stop time for an issue. When creating the Automation rule, will this populate in the queue via a column for export purposes? How will they get this information in a report?
Yes, you can add custom field to be displayed in your queue. I am not sure if queues are exportable but you can open the queue in issue navigator as in the below screenshot. In issue navigator you can display the custom field and export the issues into MS Excel
@Bloompeak Support Thank you for the update whats the purpose of the Automation rule? Looks like if I add the two custom fields to Request Type/Issue View it has to be manually entered or is the Automation rule calculating this part?
Please provide details around how to set up Automation rule if its needed.
Thank you again for your assistance.
Hi @lapacquah_bryant ,
Automation rule will calculate the custom fields. The first rule be similar to do below one.
Similarly, you will define the second rule and set the CycleTime field as
It depends on when you want cycle time to be ended. If an issue has transitioned to Done multiple times(e.g New -> In Progress -> Done -> In Progress -> Done), do you want cycle time to stop in the first transition to Done or in the last transition to Done? If you want it to stop in the first transition use the empty condition.
Thank you again.
Currently I am getting an error in the audit log and its an error on a request type that is not associated or I do not want associated with automation rule for progressStarted rule.
Thus far no calculation as occurred for either of the automation rules.
I created two different rules was this correct?
I also added both custom fields to the request type/issue view that automation rule is associated with.
Any additional detail would be great thank you.
Yes, you need 2 different rules.
If you only want the automation to be triggered for certain request types, you can add another "IF Request Type is one of" condition.
Hello, @Bloompeak Support
Does it have more to do with my smart values or the rule itself. For smart values I used what you suggested and added a condition to only capture a certain request type.
The rule produced an error, however it was for the incorrect request type, which is why I added the condition for the specified request type.
Thank you for the assistance.
Update, I fixed Automation rule and now the progressStarted populates a start time:
However, Cycle time automation rule does not populate any information and the rule is listed as "Success" via Audit log.
This is what shows in Queue:
Question, is the time listed under progressStarted considered the total Cycle Time?
Thank you for your assistance.
I found the issue and also changed the CycleTime to display seconds, instead of minutes.
However I have a few follow up questions.
1. Is there a way to stop progessstart time once ticket is closed.
progessStart is also pulling in other request types thinking it has to do with the first action which is to move tickets into various status etc. This appears to be how Automation rules operate based on the Trigger.
Thank you in advance for your assistance.
Hello @lapacquah_bryant ,
The closest you can get with out-of-the-box Jira is the Control Chart (which is available as part of Kanban Board reports). However, Control Chart offers limited details and flexibility. For maximum details and flexibility, I suggest you use a marketplace app (I know you said you can't use an app at this point but perhaps you change your idea in the future or others reading this post might benefit from this answer)
Our team at OBSS built Time in Status 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.
Here is the marketplace page for Time in Status by OBSS:
When it is about measuring the cycle time, lead time or time between any workflow statuses, our Great Gadgets app can be of great help.
It offers some dashboard gadgets that allow measuring cycle time and display it in different ways.
Cycle Time as Trend Chart - allows you to see the average cycle time for past time intervals and displays the trend
Cycle Time as Control Chart - see the issues by their cycle time and easily identify the one that took longer than expected
Cycle Time as Histogram Chart - see how many issues were in each range and how many took longer
Have a look over these articles on our blog to see what you can track with our app and how:
I hope this helps. If you have any questions, please don't hesitate to contact us at firstname.lastname@example.org.