Get the next two sprints

[Patrick]

Hello everybody,

it is possible to identify the next two sprints in a generic way?

For example, current active sprint is called Sprint 1. Sprint 2 would be the next then Sprint 3.

I was thining about some String manipulation in JQL, but didnt find something.

I need something like this, because of my two use cases:

- In our organisation, one role will check alle the upcoming issues of the next sprint

- Create a generic Dashboard for all member, to see whats in the current sprint and the tow after this. Its my workaround, because i havent found a readonly backlog or a solution to group by in a jql

Maybe someone has an idea :-)

Best regards,

Patrick

[Bill Sheboy · Accepted solution]

Hi @Patrick 

Given your sprint naming convention, you could identify the upcoming sprints with automation rules and custom fields (or a JQL scripting addon).

However, that may not help...Would you please clarify what you mean by "one role will check all the upcoming issues of the next sprint"?  What problem are you trying to solve?

Understanding that may help the community to offer suggestions.

Kind regards,
Bill

[Patrick]

Hi Bill,

for sure - the mentioned role checks all issue of the upcoming sprint, if they accomplish our definition of ready. Its the last instance before the developing team gets them for the sprint planing.

So i've an automation, that changes the status to special state for the mentioned role. Just all issues for the next planned sprint.

Maybe it helps.

Kind regards,

Patrick

[Bill Sheboy]

Thanks for clarifying, Patrick.

You may be able to create an automation rule to do that, probably with the addition of some custom fields.

But first...

• What is in your definition of ready?
• Are you able to determine if an issue is "ready" using a JQL query?

If you can write a query, perhaps you could instead use Card Colors on JQL, and so mark the issues which are ready.  This would eliminate the need for someone to review them as "ready".

[Patrick]

In our definition of ready are some points that an issue needs to fulfill, for example in case of a bug its usefull to know the date and time. So its easier for a lookup into the log-files.

The JQL query should only show up next sprint issues.

[Bill Sheboy]

If you can write JQL for "ready", then you could also add sprint IN futureSprints() to limit the results as you note.

[Patrick]

I knew futureSprints(), but this would give me all the futureSprints() and not even the next one. Or did i missed something?

[Bill Sheboy]

Patrick, let's go back to your original question to confirm what you need, as I may be overcomplicating this.  Your use case is quite unique, and different from what teams often do for backlog refinement with Scrum.

• It appears your team is pre-defining multiple sprints in advance.  Correct?
• And that issues are pre-assigned to those sprints.  Correct?
• And a specific person/role reviews those issues to assess readiness prior to sprint planning.  Correct?

If those are all correct, you probably cannot do this with out-of-the-box JQL, and so cannot do this with a dashboard easily.  (Please see below another dashboard idea.)

Instead, you may be able to write an automation rule to determine the issue list by programmatically determining the next sprint, gather the issues, and email/Slack message/etc. it to the person.

If you are able to create such a rule, you could also dynamically change a filter using automation and the REST API, and that filter could be used with a dashboard.

[Patrick]

Ok, thanks for clarifying. Maybe this would help us. Thanks a lot for help and patience :-)