As part of analyzing and exploring my team's ability to meet my company's SLA commitments,
I need to build a filter to see all issues over the last 30 days that weren't resolved in the defined time to solve them.
Some more details to build the correct filter/JQL:
- I want to get 30 previous days' data. or monthly (during August to get July data and so on...).
- Our measure to answer the SLA requirements is by delivering all bugs within the upcoming 7 days.
- Resolving bugs define by moving it to "X"/"Y"/"Y" status in the Jira board.
** Means if an issue was created and didn't resolved within 7 days since his creation he needs to be in the results even if right now it is already solved but not in the 7 defined days
Hi @Dean Kadar
I recommend you to check a short simple use case on how to get SLA time data with the help of the third-party add-on.
As an alternative, you can try Time between Statuses where you just need to set Status groups and Warnings to get Notifications.
These add-ons are developed by my team. Please, let me know if you haveany questions.
Hope it helps
My main goal is to analyze and as I explained - it is possible that a bug was not solved at the defined time (in 7 days) but was solved later during the past 30 days. I still want to see that my team didn't handle it on time.
And there is no relate to the required time (7 days) to solve it.
Hi @Dean Kadar
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.
Hope it helps.
Hello @Dean Kadar ,
The data you need is available in each issue's history but Jira does not give this as a ready-to-use report. It is also not possible to get this with a JQL query. You will need to use a marketplace app for this.
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.
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.
The app also allows you to filter issues based on report values. You can get a report like "Show me the issues (regardless of the issue's current status) that were created in July 2022 and has spent more than 7 business days in In Progress status. "
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:
Hi @Dean Kadar
Possible solutions to your use case depend on how often you need this, how much effort you want to expend, and how much money you want to spend...
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...