we have added Resolution Time pre defined gadget in the Dashboard. However, we observed that in calculating number of days a resolved ticket was open, it is taking into account weekends as well instead of just showing working days
The Resolution Time gadget (and the corresponding project report with the same name) works only based on a 24/7 calendar and ignores your calendar definitions for Jira Service Management. This gadget reports only resolved issues and leaves out the ones that are already running.
A similar gadget, Average Age Chart, behaves similarly. It only reports on non-resolved issues and does not take into account your SLA calendar definitions.
I am afraid, these Jira gadgets offer limited flexibility and there is no way to make them consider JSM calendar definitions.
If you are OK with using a marketplace app for this, 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 mainly allows you to see how much time each issue spent on each status and on each assignee.
Time in Status also has Duration Between Statuses report type which shows the duration from issue creation to a specific status or the duration between two specific statuses.
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.
Time in Status has Custom Calendar function which allows you to create as many different working calendars as needed and get reports based on them. Time in Status can also report on resolved and non-resolved issues together.
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 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.
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:
Welcome to Atlassian Community!
As an alternative, 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.
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.
Hope it helps.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events