JQL WAS Status X DURING Sprint Y

[Matthew Mims]

I'm trying to get the stories that were in status "Blocked" during a specific sprint for some historic reporting.

I know that the WAS operator is very powerful for these types of query and you can use DURING (date1, date2) however it's a real pain to have to look up the start and end dates of a sprint every time.

Is there a away to specify the sprint name and that the status WAS IN ("Blocked",...)?

To my understanding

sprint = "XYZ" AND status WAS "Blocked" 

would just return any issue that was once blocked and was once in sprint XYZ, not the intersection of these two.

This feels like a query that quite a few people would want to be using for project reporting purposes. Any ideas?

(I'm worried also that because dates and sprints don't seem to be a formal thing in jira eyes then this isn't possible - I'd be interested to understand the logic why)

[Seifallah Bellassoued · Accepted solution]

Hello @Matthew Mims

JQL does not allow filtering by sprint fields (at least in the standard).

But to meet your functional needs, I suggest to use agile reports, for example "Srpint Report". This report makes a "snapshot" of issues at the end of the sprint. So you can get "Blocked" issues at the end of this sprint.
You can base yourself on the following screenshot with the folling steps:

1. Go to reports
2. Choose "Sprint Report"
3. Choose the Sprint

I hope this can help you,

Regards,

Seif,

[Matthew Mims]

Thanks, this is a good point, although not suitable for my use case as I want to be embedding this information into confluence pages, hence the JQL.

[Mark Segall · Accepted solution]

Hi @Matthew Mims - You are correct that this isn't possible (at least not natively) and its mainly because JQL has always been 100% centered around querying issues. So, there is no option to query against a sprint and return the stories.

Your best bet is to invest in a marketplace app that provides JQL extensions. However, I know that these are quite a bit more constrained in cloud than they were in server so take that into consideration should you go this route.

[Matthew Mims]

Thanks for the clarification.