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.
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.
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.
As a SCRUM Master, one of your key tasks involves planning Sprints in your team and in order to do this, you must be able to create new Sprints and complete active ones. In order to fulfil these ta...
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