Filter for specific projects and sprints

Question

Hi community!

I want to make a filter for active sprints, specific sprints that are planned and also I want to exclude 4 specific sprints (since for some reason they are counted as open/active sprints but they are nowhere to be found in the whole jira advanced search. My JQL is the following:

project in (A, B, C, D, E, F) AND status in ("In Progress", Testing, "To Do", "Recurring Effort") AND Sprint in (openSprints(), (157, 137, 841, 963, 1017, 976, 971, 999, 1064, 263, 590, 264, 585, 998, 1037, 1032, 614, 592, 989, 114, 578, 268, 858)) AND Sprint not in (120, 459, 59, 90)  AND assignee in (Daniel Alvarez) ORDER BY originalEstimate ASC, key ASC, status DESC, summary ASC, assignee ASC, priority DESC, updated DESC

But for some reason, the filter does not exclude the 4 sprints mentioned (120, 459, 59, 90). Is something wrong in the query? How can I fix it to fetch issues from all active sprints, the specific sprints not started and ignore those 4 sprints?

Your help will be much appreciated

Daniel J. Alvarez Galo · Answer

Hi @Alan Stephenson ,

The main issue is that none of those sprints have related tickets. I used simple mode from jql to search at least for their names, still with no results at all. Here's an image of those sprints and that they don't show any issue at all...

Alan Stephenson_x1hyfv · Answer

Hello,

The one suggestion I can offer is to write a query first to see what issues appear when you do this:

project in (A, B, C, D, E, F) and Sprint in (120).

Or start with one or two projects to see what comes up.

Then, once you see what appears take a look at another query. It is possible even though you specifying a particular sprint a ticket may be part of the sprint you are trying to exclude. Without seeing some of the output it may be difficult to pinpoint.

One way is to take a single project and a single sprint or two and see what the results are, then try and see if you can make it work to exclude the one that appears.

Another idea:

Take the first part of your query, Sprint in 157. View the results of that query. See if by chance any of the tickets have sprint 120 in it.

An issue can be part of multiple sprints, and, as an issue moves through the process from sprint to sprint, ie. carrying forward the previous sprint will still be part of the ticket.

Let me know if that helps....

-alan