Hello - I am trying to get a list (either through eazyBI or a jql filter) that will tell me the time an issue went into "In Progress" to the status "Closed". The cycle time report is not helpful because it picks up from the creation date.
Any suggestions? Thanks!
If you do not want to purchase a marketplace add-on, and you have the free or paid version of Automation for Jira (A4J) from Atlassian installed... You may build this yourself:
To learn more about automation rules, please look at these references:
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nitin S_ Joshi ,
Glad that you already have found a solution that works within your current setup!
If you are still interested in what are eazyBI possibilities regarding this, you can explore some examples that we have regarding Age, Lead and Cycle time in our demo account: https://eazybi.com/accounts/1000/dashboards/7513-age-lead-and-cycle-time
One particular report explores multiple ways on how to calculate Average lead and cycle times: https://eazybi.com/accounts/1000/cubes/Issues/reports/499777-average-lead-and-cycle-time
You can easily export and import report definition into your account, to see how it works with your data and adapt the report to your need from there: https://docs.eazybi.com/eazybijira/learn-more/training-videos#Trainingvideos-Episode7:HowtogetreportsfastfromeazyBIDemoaccount
best,
Gerda // support@eazyBI.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you all for your input! Going to try the Automation approach as we already have that in our jira software. Will look at the other add-ons as well.
Cheers!
Nitin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nitin S_ Joshi ,
You can try Status Time app developed by our team at Bloompeak. It provides reports on how much time passed in each status as well as status entry dates and status transition count.
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(eg. average in progress time per project). And all these are available as gadgets on the dashboard too.
Here is the online demo link, you can see it in action and try.
If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nitin S_ Joshi ,
You can use Enhancer Plugin for Jira's Time between custom field for this.
It's so easy to configure: Go to Enhancer Plugin for Jira menu > Duration custom fields > Add new custom field > Time between custom field. You can select from status to status and you're done.
Later, you can enjoy gadgets and export these fields.
Please let me know if you have further questions.
Cheers,
Gökçe
Please note that I'm one of the members of the Snapbytes team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Nitin S_ Joshi ,
Jira does not give built-in flexible reporting options about this. You can try getting the history data either directly from database or REST API to calculate this yourself. You can also use some workflow functions to implement custom measurements but will probably be hard to maintain.
For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 assigned to each assignee. You can combine statuses in any way into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the total InProgress time per Epic, or average resolution time per issuetype).
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.
The app has Custom calendar support which means you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)
Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.
Using Time in Status you can:
Timepiece - Time in Status for Jira
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.