JQL query to calculate the 'next' Sprint and issues, when I have multiple future sprints planned

[chad_leblanc]

So I am trying to filter on a Kanban board, the next sprints' cards, but ONLY the next sprint.  I work with sprints that are created 4-5 ahead of the current one.  I am at a loss since we use a Scrum board for the backlog, and that's where all of them would pull from.

I've tried using Jira's AI, Gemini, CoPilot, and ChatGPT and all are giving different responses, and they always seem to suggest scripting that is not available in my instance.

Has anyone successfully done this?

[chad_leblanc · Accepted solution]

project = <<insert Project>>

AND issueFunction in nextSprint("<<insert Board>>")

AND statusCategory != Done

ORDER BY created ASC

[Khai]

@chad_leblancthis is very helpful with what I need right now. Is there also a JQL for me to pull  tickets 5 days before the start of the next sprint?

[chad_leblanc]

You can try this - 

project = <<insert Project>> AND issueFunction in nextSprint("<<insert Board>>") AND statusCategory != Done AND createdDate >= startOfDay(-5d, startOfNextSprint()) ORDER BY created ASC

I also used ScriptRunner Enhanced for more items to add into JQL that are not native

[Dick]

Hi @chad_leblanc, welcome to this community.

Jira is all about supporting the agile way of working. When I read your question, I cannot help wondering why you would like to have 4-5 sprints ahead of the current one. 

Time spent on arranging these sprints could also have been used to update the backlog. Agility is best obtained by being flexible in the uptake of the Jira-items that add the most value for the customer in nothing more than the upcoming sprint. 

My two cents are not on AI, not on 4-5 "pre-sprints", but on the essence of the agile manifesto.

;)

[chad_leblanc]

I appreciate the input, we use additional sprints to separate work from the backlog into different areas (our offshore team for one, blocked work for another) and those just get included in the search.

I did, however, see that we had available the ScriptRunner Enhanced Search and that allowed me to use additional coding that is not native to Jira to complete the job.

I'll post the steps that worked out for my use.

[Dick]

Ah, so the 4-5 sprints are more like parallel sprints rather than consecutive sprints. 

I would suggest having a project defined for the offshore team, as their work should reside on their project. (they still can contribute to other projects by using links). 

[chad_leblanc]

I wish I could! I'm limited to my company-controlled boards and my admins don't see a need to change this if it's been working for so long (I have only just begun to really try and fix the issues on our team about this).

[Dick]

You can combine projects in the Jira Plans View (Roadmap view) and have a Gantt chart visible that can help you plan the work and the interactions between different teams. 

It can provide you with information on the critical path to reaching certain goals. 

We use it in our University to map out the next quarter increments we hope to achieve.

[chad_leblanc]

I'll have to see what I can do from my end!  I appreciate that!

[Dick]

We're here to help, there's a lot of experts here that know a lot more than I do. It's a good thing you found us.