how to refer the current sprint in the query?

[Mahadevan Hariharan]

I created a custom board to filter my tasks only for the active sprint.  everytime, i need to refresh the sprint in the board.  is there a constant that refers the active sprint so that I don't need to change everytime sprint advances?

[Haran Kumar · Accepted solution]

Hi @Mahadevan Hariharan 

Project = "test project" AND sprint in openSprints()


Note: Replace test project with your project name. 


Hope this helps


Regards

[Haran Kumar]

You can fine tune more with following Statement and so on, 

Project = "test project" AND sprint in openSprints() AND resolution = unresolved 

Note: Replace test project with your project name & use resolution key as per your terminology . It may be pending, unresolved , tobetaken anything. Kindly use accordingly .


Regards

[Mahadevan Hariharan]

Thanks!  it works. openSprints() only works with "in" and not with "-"

[Aileen Leitner Buck]

When I use this query it does not pull in any user stories or tasks that have rolled over from previous sprints. How do I include those in my query?

[Nk Mk]

@Aileen Leitner Buck - Is this still a problem for you?

I've just tried this on my JIRA board using the following...

project = MAJ AND Sprint in openSprints() Order by Rank ASC

We have quite a few +1 tickets that have rolled over from, e.g. Sprint 22 to 23 and these are visible for us.

[Michelle Hurtley]

Yes! @Nk Mk  Thank you so much for this answer. It's exactly what I was looking for. 

[ralphsmith80]

This doesn't actually reference the current sprint. It references all open sprints. This can be an issue if you create a sprint early for staging, but you don't start the sprint until it's ready to go. 

[Jeimi Herrera]

Thanks, @Haran Kumar This was very helpfully.

[Prateek Sharma]

We can also try below Jql query, here we have removed closedSprint - the previous completed sprints & the future sprints. This Jql query gives you stories part of active sprint.

issuetype = Story AND Sprint not in (closedSprints(), futureSprints())

[Stephen Bull]

this also excludes items rolled over from previous sprint. anyone have any solutions for this? As we are planning a full quarter as per scaled agile, future sprints are populated to some degree, but we also have some level of rollover. Any ideas? thanks