Centralized Sprint Management

[Krishna P G]

I have a project named Demo, within which I’ve created five Scrum boards, each representing a different Scrum team. All teams are expected to follow a common sprint cycle at all times.

Objective:
When I create sprints in the Demo Scrum Board, I want those sprints to be automatically visible in each of the individual team boards, even if no work items (e.g., Stories) are assigned to those sprints yet.

Observation:
Based on my exploration, sprints created in the Demo Scrum Board do not appear in the individual team boards unless at least one issue is explicitly assigned to each sprint in each board.

Could you please advise if there’s a more effective way to achieve this objective?

[Alexey Pavlenko _App Developer_]

Hi @Krishna P G ,

Please read this. I think the parallel sprints is what you need. Once enabled, add concrete filters to each Scrum Board.

Best regards,
Alexey

[Krishna P G]

Hi @Alexey Pavlenko _App Developer_ , thank you for the inputs.

In Parallel sprint, each sprint can be started and completed independently and we dont want that to happen as each team should work on same sprint.

[Gautam Jagthap]

I'm new in this but from my knowledge, A sprint only shows up on a board if it has at least one issue that matches that board’s filter.

Here are some options to consider:

• Shared Filters: Make sure all team boards use filters covering the same projects or issue types as the Demo board. But sprints still need issues in those filters to appear.
• Placeholder Issues: Create a dummy issue for each team in every sprint to keep the sprint visible on all boards.
• Single Board with Filters: Use one board for all teams and apply quick filters to separate their views. This way, all sprints are visible to everyone.
• Automation: Set up Jira Automation to add placeholder issues automatically when a sprint is created. This needs admin rights and some configuration.

[Krishna P G]

Thank you @Gautam Jagthap for your feedback, I will continue to create the dummy issues into each sprint. 

[John Elder]

This has been my experience also, with similarly sized projects.  The main "Scrum" board is where all sprints are created, started, and stopped, and the team boards only have the Sprints display when issues assigned to that team are present within one of the sprints.  My teams do Sprint Planning 1 based off the main Scrum board, then do Sprint Planning 2 and daily sprint management via their team boards.  There is no backlog management done on the team boards, themselves.

In the case where I need backlogs to be separate by team, I allow those teams to create, start, stop sprints on their individual team boards.

You are definitely not wrong, but I don't know a way specifically around it.

[Krishna P G]

Thank you @John Elder  for your feedback, it gives me confidence that I am in the right direction.

I am planning to create an automation rule that will auto create dummy issues into each of the team when a sprint is created, Thanks.