All issues belonging to sprints within a date range

[Nick]

Hi,

Use case: I want to supplement a report for the last year that returns ALL the issues assigned to sprints whose start/end dates were in-between a given range. Let's say Jan 23 - Jan 24.

Thanks!

N

[Trudy Claspill]

Hello @Nick 

Native Jira functionality will not enable you to extract that data with a filter or native gadget.

Do you have or are you willing to consider purchasing a third party app to meet your requirement?

Is this an ongoing need or a one time need?

You might be able to use a combination of REST API calls to get the information you need.

[Nick]

Thanks for the reply @Trudy Claspill - It's a one-time need for now, but it does sound like pretty basic functionality to be honest.... And if were it straightforward, we'd make heaps of use out of it for retro reporting. . I.e. "What did we deliver in q1, h2, fy"?

[Nick]

What was the third-party app you were thinking about @Trudy Claspill

[Trudy Claspill]

Why do you want to base delivery on the issue being assigned to a sprint in the date range? Being assigned to a sprint doest mean the work was completed.

When issues are moved to a done/green status, the Resolution field should be getting set. And if they are reopened the Resolution field should be getting cleared. That is handled automatically in Team Managed projects and it should've been incorporated into the workflows for Company Managed projects. Setting/clearing the Resolution field sets/clears the Resolved date/time fueld.

Assuming that the last status in you Scrum boards is a done/green status, you could filter based on the Resolved date field being within your date range.

[Nick]

@Trudy Claspill 

I can't get the JQL ton run based on "Resolved" date, though? There's "Resolution", Resolution date" and "Resolved date" - none of which are returning anything for me.

And, while a sprint doesn't mean the work was done, surely another filter on "Status" would do the trick?

[Trudy Claspill]

Hello Nick,

Yes, "Resolved" can be used in JQL filters to select issues based on the date the Resolution field was set.

https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Resolved

If that isn't working for you please provide a copy of the JQL you are trying to use, and tell us in what way it isn't working. Is there an error message? Are you not getting the results you expect?

Have you double checked an issue that you think should be in the results to confirm the Resolved date is actually set and in the range you specified? The Resolved date can be seen in individual issues on the right below the More Fields panel. You can also add it to the columns displaying the search results.

Using the Resolved field is the best native solution, assuming that your workflows are properly configured to set and clear the Resolution field.

If you don't find that to be an acceptable solution and require the ability to select issues based on inclusion in a Sprint where both the Sprint Start and End Dates are within a date range, that won't be possible with native functionality. It might be possible with a third party app. I have not researched each of the search-extending apps to see if any of them could fulfill this use case.