How can I see three future concurrent sprints?

[Eric Bailey]

Our company has a single backlog that feeds (based on priorities and lines of business) 3 separate teams that run 3 concurrent sprints.  

REFERENCE:

- Sprint 14 - Team 1

- Sprint 14 - Team 2

- Sprint 14 - Team 3

As such, they each have their own future sprint

- Next Sprint - Team 1

- Next Sprint - Team 2

- Next Sprint - Team 3

We will be planning work for each of these teams as such

- Planning - Team 1

- Planning - Team 2

- Planning - Team 3

We have dashboards to pull up work and obviously, the 3 active sprints are easy to visualize using OpenSprints().  

PROBLEM:  On our dashboards, we would also like to to be able to filter on the 3 Next sprints without including the Planning work.  FutureSprints() will pull in all 6.  Scriptrunner NextSprint will only pull in Next Sprint - Team 1.  

QUESTION:  Is there a way to pull in just the 3 "Next Sprint" work?

[Habib__Plugio__ · Accepted solution]

Hi @Eric Bailey 

You can use `sprint in openSprints(), futureSprints()` combined with a JQL filter for the specific team field if you have one.

Or, if your sprints are named consistently, you might be able to use a JQL clause like `sprint ~ "Next Sprint - Team*"` to catch all three.

Irrelevant from question, our Sprint Health Monitor  might be useful for your use case. You visualize up to 4 sprints in a single screen.

— Habib, Plugio team

[Eric Bailey]

Thank you.  I will try the JQL.  I also thought (after I submitted this, of course), that it is possible that all 3 next sprint will remain.  The process would be something like

- Groom Next Sprint (if not already done....we just started this structure, so most likely, not all of this volume has been groomed)

- Create Sprint 15

- Move Next Sprint tasks into Sprint 15

- Groom Planning Sprint for each team

- Move Planning sprint tasks into Next Sprint for each team

In this case, the "Next Sprints" would remain evergreen, so would always be Sprint IN (823, 824, 825), as the "Next Sprints" are actually place holders until we are ready to load the actual sprint.

NOTE:  The Next Sprints were set up without timelines, whereas the new sprints will be timeboxed.  

[Paul Glantschnig _Appfire_]

Hello @Eric Bailey,

The evergreen placeholder idea keeps the sprint IDs stable, which is the hard part solved.

One note or option in case the dashboard side stays fiddly: if a Marketplace app is an option, JXL for Jira takes any JQL, e.g. your sprint IN (823, 824, 825) included, and shows the result grouped by sprint, so all three Next sprints sit in one view as collapsible sections.

Sum-ups per group show story points or issue counts per team at a glance, which is handy for watching the load while you groom. Inside each sprint you can group further by assignee or team, and a saved view turns the three-sprint check into one click rather than a set of gadgets.

Roughly like this:

For transparency, I'm on the team that makes JXL.

Cheers, Paul