Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira filter to show throughput over time period

Louise Boulton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 16, 2020

Could anyone sanity check this approach to getting throughput by sprint?

My JQL is project = XYZ AND resolutiondate >= 2020-05-21 AND resolutiondate <= 2020-06-03 AND resolution not in (Duplicate, "Won't do", "Not Applicable") AND issuetype != "Sub Task"

The date values represent start and end of a sprint. I have a spreadsheet containing two columns: Sprint, and Number of Issues Completed. I enter the relevant sprint and the number of issues returned by this query and generate a line chart in the spreadsheet with sprints on the horizontal axis and numbers on the vertical axis.

Grateful for any responses and thanks in advance.

2 answers

0 votes
Emre Toptancı _OBSS_
Atlassian Partner
July 17, 2020

Hello @Louise Boulton ,

Time in Status app by OBSS can be utilized for this purpose (among other things).

We prepared a new use case document that explains how to calculate throughput for, multiple time periods, using Time in Status by OBSS. You might also want to check it out:

https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=303795348

You can find the app here: Timepiece - Time in Status for Jira

EmreT

0 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 6, 2020

Hi Louise,

welcome to the Atlassian Community.

A JQL query and a subsequent export to spreadsheet tooling like Excel would be, indeed, an option. This requires some manual interaction, though - but it is absolutely doable.

Have you also checked the built-in reporting options for Jira Software?
https://confluence.atlassian.com/jirasoftwareserver0713/reporting-965542783.html

In several cases this already fulfills the requirement.

The JQL query will most probably show open issues (you have excluded some common statuses that indicate somehow closed issues) that have a date of resolution between two fixed dates. Additionally Sub-Tasks are excluded and the query is bound to one specific project.
In case the requirements change the query needs adaption. The date range is probably best to be replaced by relative dates as soon as 2020-05-21 and 2020-06-03 are not relevant criteria anymore.

Cheers,
Daniel

Suggest an answer

Log in or Sign up to answer