JQL to return all incidents closed by week for the previous month

[Surti K]

Can someone assist with this JQL ?

Trying to get a row count of Incidents closed by week for the previous month.

Tried this 

project = Test and resolution=Done and startofWeek>= ("-47d") and endOfweek <= ("47d")  

The hope is to get a row count per week for the month of Dec and the 1st 2 weeks of Jan. 

Any help greatly appreciated

Thanks

[Valeriia_Havrylenko_SaaSJet]

Hi @Surti K 

Try this JQL: 
project = "XXYXXCC" AND issuetype = "Production Bug" AND created >= 2022-02-07 AND created <= 2022-02-13 AND status != Closed AND status != Resolved AND Not status changed after startOfWeek("-1")

And if you are already switched to the cloud or data center version, you can try Time in Status for Jira (developed by my SaaSJet team)  Transition Count report shows how many times an issue has moved between all statuses in the workflow. You can also filter issues by date, so you will get row count of Incidents closed by week for the previous month easily! 

Add-on has a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌

[Gizem Gökçe _OBSS_]

Hello @Surti K ,

As far as I understand, your primary choice is not a paid solution, but if you would like to evaluate it, I would like to introduce you to a very advanced tool with which you can easily access the reports/results you request. 

I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for both  Jira Cloud, and Data Center. 

Our app has a free 30 day trial and is free for up to 10 users. So please feel free to give it a try and present it to your team.

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. In addition, you can see how many issues have been closed/resolved in different time periods, as you try to achieve in your JQL statement. (Please see the screenshot below, the following report is grouped by the resolved date. So you can see that only 3 issues were closed between 10th and 16th December)

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

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. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

[Trudy Claspill]

Hello @Surti K 

Welcome to the Atlassian community.

startOfWeek a value that you use on the right side of the comparison; i.e.

created < startOfWeek()

You use it as a comparison to a date/time field that exists in the issue, like "created" or "updated".

Refer to the documentation for more information about the startOfWeek() function:

https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-functions-reference-939938746.html#Advancedsearchingfunctionsreference-startOfWeek

I recommend that you instead look at using the Created Vs. Resolved report gadget that is available when you create a Dashboard. You can find more information about Dashboards here:

https://confluence.atlassian.com/jiracoreserver/configuring-dashboards-939937983.html

The Created vs. Resolved graph will give you more information (how many issues were created) than you need but it is a simple way to see the number of issues Resolved per week over a period of time.

Note that the Resolved count is based on the Resolved Date/Time of the issue, and the Resolved Date/Time of an issue is set/cleared when the Resolution field is set/cleared. So, if you are no properly managing the setting and clearing of your Resolution field, then the chart will not provide you with good data. It is not possible to change that chart to be based on the date/time issues changed to a specific Status.

[Surti K]

Thank you for the pointers Trudy. Much appreciated.

Will review these recommendations. 

Thanks