inSprint() JQL Function Missing

I am not able to use the inSprint() JQL function.  It is not listed in the module list of the ScriptRunner plug-in and therefore I cannot enable it.  I have the latest version of the plugin, i.e. 3.0.16.



2 answers

1 accepted

Try with "Sprint in ...", here you can use several functions (openSprints, closedSprints, futureSprints)

I need inSprint() because I need to query for the issues in the backlog.

What do you mean with "query for the issues in the backlog" ? Something like resolution is EMPTY AND Sprint not in openSprints() AND Sprint not in futureSprints() should do ?

I need to get a list of issues in the Backlog of an Agile Board. I have tried many different combinations and can't seem to get the correct issues returned. The one you suggested returns half of the issues on the backlog.

Ok, i forgot the issues that where never linked to a Sprint. Also you have to complete the filter somewhat (ecluding subtask issues, Epics). At my side, this gives exactly the issues in the backlog of a board: resolution is EMPTY AND ((Sprint not in openSprints() AND Sprint not in futureSprints()) OR Sprint is EMPTY) and issuetype not in subTaskIssueTypes() and issuetype != Epic

We ran into a similar problem trying to show only epics related to issues that appeared in a RapidBoard's backlog, current or future sprints. To do this we used Jamie Echlin's script runner plugin and the following RapidBoard query:

Simple Rapid Board based on single project:

project = "My Project" or issueFunction 
in linkedIssuesOf("
project = 'My Project' and (sprint is empty or 
Sprint in (opensprints(), futuresprints()))", "has Epic") order by Rank 
ASC

'Complex' RapidBoard based on multiple projects

filter="Complex RapidBoard Filter" or issueFunction 
in linkedIssuesOf("filter='Complex RapidBoard Filter' and (sprint is empty or 
Sprint in (opensprints(), futuresprints()))", "has Epic") order by Rank 
ASC

 

This approach allows us to utilize the same rapid board filter syntax (changing the project name) and only shows the Epics that are associated with issues which are in the backlog, a future sprint, or a current sprint.

Note that applying this filter to a RapidBoard that was built automatically by JIRA Agile for a single project could result in displaying fewer Epics than the Board shows now - this is because the Epics which do not appear are not associated with any issues in your Board's backlog or current/future sprints.

 

Hope that helps someone.

-wc

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published yesterday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

37 views 0 3
Read article

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