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)
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.
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".
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:
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.
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.
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).
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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!
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