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
I am currently using ''Resolution Time'' and ''Closure Time'' Dataplane reports to determine the average time from status OPEN to CLOSED for project tickets.
The issue I have with the data is that, in my workflow, a ticket can go from status 'OPEN' to 'CLOSED' (cancelled resolution) without having been in status 'RESOLVED'. Therefore, the ''Resolution Time'' report has inaccurate data as it does not take those tickets into account.
Also, I have tickets that follow the workflow as such : 'OPEN' - 'IN PROGRESS' - 'RESOLVED' and remain in status 'Resolved' for some time before going to status 'CLOSED' (and some never do!). So, data from the ''Closure Time'' report is also not valid because :
1) Tickets can remain in status 'RESOLVED' for weeks before status is changed to 'CLOSED' so my closure time is inaccurate.
2) Tickets in status 'RESOLVED' are not picked up by the ''Closure Time'' report when I'd want to consider them 'CLOSED' even if not in that status.
Is there a report (or JQL) I could use that would give me the REAL resolution time from ANY open STATUS to either RESOLVED or CLOSED? What would be your recommendations?
Thank you so much!
Hello @[deleted] ,
First of all, most Jira reports that deal with issue resolution does not care about Resolved or Closed statuses. It all comes down to Resolution system field.
For Jira, an unresolved issue is one that does not have a value for Resolution field. It is usually displayed as "Unresolved" on issues. A resolved issue is the one that has a value (any value) for the Resolution field.
The good practice is to provide some type of Resolution for your issue in all possible end cases. If your issue is resolved successfully then the resolution might be "Done". If it is canceled, the resolution might be "Cancelled", and so forth. If the issue has reached the Resolved or Closed status in any way, it must have a resolution set for it. This way, all Jira reports that rely on the resolution field will function correctly.
In addition to what I said above, you can get very good reports for your needs using our app. Our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud, and Data Center.
Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Resolution Time, Cycle Time, or Lead Time. For example, you can add a column to the report that includes all statuses in your workflow (except resolved and closed) and see the total time between creation and resolution of the issue.
You can calculate averages and sums of those durations grouped by the issue fields you select. (For example, see the total InProgress time per Epic or average Resolution Time per issue type).
Below are screenshots that show a custom Lead Time field that shows the total of ToDo and InProgress statuses. The same can be done for any status combination.
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.
Using Time in Status you can:
Hi @[deleted] ,
As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count. For you specific case, inside the report you can group all statuses except "resolved" and "closed" into "resolution time" and get resolution time report exactly as you need.
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.
Hi community! 👋
For anyone looking for an answer to this question
Are you company switching to Cloud or Data Center?
If not, I guess Time Between Statuses will be an option. We still provide support for add-on server version and we help to install it. This add-on, which measures connections in the workflow, through a transition time in specific issues. You can calculate the processing time like ''Resolution Time'' and ''Closure Time'' with add-on easily!
This add-on developed by my team.
As an alternative , and if you switching to a cloud version, you can try Time in Status for Jira Cloud. The primary purpose is to help teams gather valuable data about the lifecycle of your issues in Jira. Add-on allows you to measure and visualize the time spent in each status, such as "Open," "In Progress," "In Review," and "Closed," and provide 7 types of reports to help you identify areas for improvement. Add-on developed by my team.
Add-ons have a 30-day free trial version and free up to 10 users.
Please, let me know if you have any questions
Hope it helps 😌