how can I filter issues not in active sprint (i.e. in backlog) for my dashboard?

I have configured my JIRA dashboard to show my 'In Progress' issues and 'Assigned to me" issues. The 'Assigned to me' includes both issues from the current sprint, and issues that are in backlog. What I want to create is a filter for 'Active in sprint' and another for 'Waiting in backlog', so I can more quickly see what I should be working on next. I can't see any existing filter attributes that will allow this.

My current filter is this;

issuetype = Story AND status in (Open, Reopened) AND assignee in (currentUser())

Is there some attribute that would support something like;

issuetype = Story AND status in (Open, Reopened) AND assignee in (currentUser()) AND xxx in (Backlog)

8 answers

1 accepted

8 votes
Timothy Chin Community Champion May 21, 2013

You can add "AND sprint is not EMPTY". Though the JQL will not tell you whether the Sprint is active or not.

EDIT: Oh wait, there is "sprint in openSprints()" that you can use.

"AND sprint is not EMPTY" didn't work as a couple issues that had been in a sprint, but were moved back to backlog still open when the spring closed, were still listed. "sprint in openSprints()" seems to work better. Thanks.

is sprint in openSprints()supposed to show issues from the backlog? For me it doesn't. I need to view issues only from the backlog for a specific component for the purposes of the backlog refinement.

I have found that to identify issues that are in the backlog, I have to say

sprint IS EMPTY OR sprint NOT IN openSprints()

That is to say sprint NOT IN openSprints() is not enough: it doesn't select issues that have no sprint field at all.

Good one Martin. I used something slightly similar as well:

... AND (sprint is EMPTY or sprint in closedSprints()) ...

I used closedSprints() because if an issue wasn't finished in a previous sprint then that value is still present ... realized that the sprint field is more like a history/array.

... AND (sprint is EMPTY or sprint in closedSprints()) ...

1. JQL for Backlog: With Script Runner plugin (by Jamie Echlin) installed you can try: issueFunction in inSprint("My board", "Backlog")

General Function: inSprint(board name, sprint name)
Finds issues in the given sprint. This works for sprints that are not yet started, active, and completed sprints. Instead of the sprint name, you can also use the string "Backlog".

https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-inSprint(boardname,sprintname)

2. JQL for open Sprints: sprint in openSprints() (as Timothy already mentioned)

I had developed my query initially in "Basic Mode", and switched to advanced mode to paste the query in my post. Now that I added the "sprint in openSprints()", JIRA tells me it's "too complex to display in Simple mode". Starting in Basic Mode had led me to believe the options were far more limited than they actually are.

>> Starting in Basic Mode had led me to believe the options were far more limited than they actually are.

Yes, that's true. Advanced mode is very powerful.

>> tells me it's "too complex to display in Simple mode".

More about switching between modes:

https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-switchingSwitchingbetween%27Advanced%27and%27Simple%27Search

In general, a query created using 'Simple Search' will be able to be translated to 'Advanced Search' (i.e. JQL), and back again.
However, a query created using 'Advanced Search' may not be able to be translated to 'Simple Search' (and in this case it is not possible).

On the other hand it is still not possible to create filter with something like 'Waiting in backlog' without additional plugin.

Hi,

The statement below seems to work for me:

Sprint not in (opensprints(),futureSprints()) or sprint is EMPTY

In addition to an open sprit I have a number of futuresprints where we prepare the next sprints.

NB. the order of the arguments is important. If for example the statement sprint is empty is placed before sprint not in etc it renders an empty set.

Kind regards,

Max

0 vote

There is an opened Request for that here:

https://jira.atlassian.com/browse/GHS-6036

I use successfully the following JQL query to match what the backlog list shows in JIRA scum plan mode, assuming project is "PRJ" and current active sprint is "Sprint 6":

 

project = PRJ AND (Sprint != "Sprint 6" OR Sprint is EMPTY) AND status in ("Open","In Progress") AND type not in  (Sub-task,Epic) order by rank

 

It kinda makes sense if you think about it, that if there is no value in the sprint field then it can't compare it against a list of sprints, although confusing. My filter now works by checking for issues that are neither in openSprint or empty as well as neither in closedSprint or empty … so that hopefully is returning all issues that may or may not be included in a sprint (but not a closed one and not the currently running one) and then I can check for those issues with no story points assigned to create a view showing all issues requiring story point estimation (excluding stories in sprints that have already started or are now closed).

"sprint in futureSprints()" 

Not sure if openSprints changed and futureSprints was added but openSprints seemed to show the active one.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,198 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot