Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Knowing when you have a Shared Sprint

When using parallel Sprints in JIRA Software, you're able to run multiple active Sprints simultaneously.

Often enough when working with multiple Sprints, they can sometimes get mixed up and create what is known as a "Shared Sprint". 

Sprints aren't dependent on any Board or Project meaning they are not bound to the Board they were created in and can live across multiple Boards at the same time. This means that it is possible for a Sprint to be displayed in more than one Board.

Although displayed in multiple Boards, it remains one entity and any changes made to the Sprint in one Board will be reflected in all other Boards where the Sprint is displayed as well. This can be intentional or in most cases erroneously.


How can I "accidentally" create a Shared Sprint?

  • The Board includes Issues from more than one Project (project in (TEST, AGILE) ORDER BY ASC) and was added when dragging and dropped unwittingly
  • When editing the Sprint field, the Issue was added to the wrong Sprint when there's more than one with the same name
  • The Issue was moved from one Project to another, keeping the Sprint field value


What are the indicators that suggest you're dealing with a Shared Sprint?

  • A Sprint shows up in a Board in which it wasn't created in.
  • Making a change to a Sprint in one Board affects a Sprint in another Board.
  • A Sprint shows up in a Board after an Issue has been moved to it from another Board.
  • Attempting to close a Sprint requires admin permissions in another unrelated Project.


How can I confirm if the suspicious Sprint is indeed a Shared Sprint?

  • If changes to one Sprint affects a Sprint in another Board. Verify that these are indeed two different Sprints by checking on their IDs.


  • Use the Issue Navigator to search for issues in each Sprint using the Sprint ID. If any of the Sprints contain Issues from more Boards, it will be displayed in all of them.



To avoid such confusion, it is recommended to always use unique names when naming Sprints (like including the project key) so that they are easily identified.


I've accidentally created a Shared Sprint, what now?

  1. Identify the Sprints that are incorrectly included to the Board, referring to their Sprint ID
  2. If one Sprint is used where there should be two, create a new Sprint in the Board that is missing one.
  3. Move the Issues to their respective Sprints by editing their Sprint field value. For large amounts of Issues, this can be done with one bulk operation.


  1. Identify the Sprints that are incorrectly included to the Board, referring to their Sprint ID
  2. If there should only be one Sprint, remove the none relevant Issues to the Sprint by emptying their Sprint field value.


Additional information

This is applicable for both Next-gen and Classic Software Projects. In efforts to stop the accidental creation of Shared Sprints, the feature request to restrict Sprints per Project was created:

By adding yourself as a watcher you will receive all communications done on the progress of this feature request.



Log in or Sign up to comment

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you