Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,397
Community Members
 
Community Events
168
Community Groups

FILTER/JQL to filter all issues over the last 30 days that wasn't resolved

Hi community,

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

6 answers

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.

 3.png

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

saralie s_ Community Manager Aug 11, 2022

@Anthony Kozlov_SaaSJet_ Please review our guidelines for Marketplace and Solution Partners. When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. 

Is this applicable for your need?

updatedDate < startOfDay(-30) AND resolution is empty order by createdDate DESC

Hi,

Unfortunately, no.

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.

0 votes
Bloompeak Support Marketplace Partner Aug 12, 2022

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. 

  • This app has a dynamic status grouping feature so that you can generate various valuable reports as as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).
  • You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
  • Status durations are calculated according to the working calendar you define. 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.
  • You can set different duration formats.
  • You can export reports in CSV file format and open them in MS Excel.
  • You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
  • You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a free solution, you can try the limited version Status Time Free.

Hope it helps.

0 votes

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

tisCloud_StatusDuration_LeadTime_with Estimates.png  tisCloud_AssigneeDuration.png     

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.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

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.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
  • Export your data as XLS, XLSX, or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets

https://marketplace.atlassian.com/apps/1211756/

EmreT

0 votes

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...

  • Need this one-time/infrequently: export your issues to a spreadsheet and perform the analysis in that tool
  • Need this often, and do not have money to spend on addons: learn about automation rules, add a custom field to store the Lead Time (time from created to resolved), and create a rule triggered on transition to done to calculate the field.  Then you can just report/dashboard using JQL on the custom field.
  • Need this often, got money to spend, and do not wish to expend too much effort: investigate Atlassian marketplace addons to report this measure.

Kind regards,
Bill

0 votes
Rahul_RVS_Support Marketplace Partner Aug 10, 2022

Hi @Dean Kadar 

If you are fine with a mktplace app, you can try out our add-on to get this data. You can group your statuses to define the resolution/cycle time, and filter issues which exceeded the specified days in resolution time.

 Time in Status Reports 

 

TIs - Status Suration.PNG

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

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...

5,073 views 18 32
Read article

Atlassian Community Events