> * Begin of the insertionSharing is a project-level setting, not a sprint-level one (like with versions at the moment). Users can chooseEnd of the insertion Begin of the deletion We will have sprint sharingEnd of the deletion in the Begin of the insertionproject settings:End of the insertion Begin of the deletion initial version.End of the deletion
>
> * Begin of the insertionShare sprints - Sprints can be created in this project. All those created sprints are sharedEnd of the insertion Begin of the deletion It simplifies migration from versions and is what we wantEnd of the deletion to Begin of the insertioneither (user selection):End of the insertion Begin of the deletion have later on anyway.End of the deletion
>
> Begin of the insertion End of the insertion * Begin of the insertionAllEnd of the insertion Begin of the deletion A sprint will have the same status across allEnd of the deletion projects Begin of the deletion it is shared with.End of the deletion
> Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion > Begin of the insertion End of the insertion * Begin of the insertionSubprojectsEnd of the insertion Begin of the deletion Sprints can only be activated by a user having the `manage_sprints` permission in the project from which the sprint is shared.End of the deletion
> Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion > Begin of the insertion End of the insertion * Begin of the insertionNo sharing -End of the insertion Sprints can Begin of the deletion thus also onlyEnd of the deletion be Begin of the insertioncreatedEnd of the insertion Begin of the deletion activatedEnd of the deletion in Begin of the insertionthis project. None ofEnd of the insertion the Begin of the insertioncreated sprints are shared with any other projectEnd of the insertion Begin of the deletion sprint from which it is shared.End of the deletion
> Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion > Begin of the insertion End of the insertion * Begin of the insertionReceive shared sprints - No sprintsEnd of the insertion Begin of the deletion Trivial but for clarity: If the sprint is not shared, then itEnd of the deletion can Begin of the deletion onlyEnd of the deletion be Begin of the insertioncreated within this project. Instead sharedEnd of the insertion Begin of the deletion activated in the project it is defined in.
>
> * This all results in that we currently cannot prevent the collision of two activeEnd of the deletion sprints Begin of the insertionare used.End of the insertion Begin of the deletion in the following case:End of the deletion
> Begin of the deletion
> * There is already an active sprint in the project.
>End of the deletion
> Begin of the deletion End of the deletion * Begin of the insertionStatus, Name and dates of aEnd of the insertion Begin of the deletion A sharedEnd of the deletion sprint Begin of the insertionare also shared (can't be different per project)End of the insertion Begin of the deletion is activated OR an active sprint is shared.End of the deletion
> Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion > * Begin of the insertionOnly one projectEnd of the insertion Begin of the deletion WeEnd of the deletion can Begin of the insertion"Share with all projects".End of the insertion Begin of the deletion prevent the case where:End of the deletion
>
> * Begin of the insertion\[open\] Possibly, define systemwide sprints not withinEnd of the insertion Begin of the deletion There is alreadyEnd of the deletion a Begin of the deletion sprint (shared or not) active in theEnd of the deletion project Begin of the insertionbut outside of it. It could then be guarded by a global permission.End of the insertion
>
> Begin of the deletion End of the deletion * Begin of the insertionSprint sharing is only possible if enabled firstEnd of the insertion Begin of the deletion The user tries to activate another sprintEnd of the deletion in the Begin of the insertioninstance administrationEnd of the insertion Begin of the deletion project.End of the deletion
> Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion > * Begin of the insertionOnly sprints fromEnd of the insertion Begin of the deletion The case we cannot prevent isEnd of the deletion one Begin of the insertionsharing project are received. If there are multiple projects from whichEnd of the insertion Begin of the deletion we probably want to support later on anyway and have to deal with suchEnd of the deletion a Begin of the insertionreceiving project could take its sprintsEnd of the insertion Begin of the deletion situation. As long as we don't haveEnd of the deletion the Begin of the insertionorderEnd of the insertion Begin of the deletion notionEnd of the deletion of Begin of the insertionpriorityEnd of the insertion Begin of the deletion an "active" sprint anyway (with automatism in place for board generation) this might not be an immediate problem.
>
>
> Addendum:
>
> * We also cannot prevent it in the case where a sprintEnd of the deletion is Begin of the insertionas follows (lowestEnd of the insertion Begin of the deletion first shared with its sub-projects and then, in a project above, another sprint is shared with that project's sub-projects. That leadsEnd of the deletion to Begin of the insertionhighest priority):End of the insertion Begin of the deletion having multiple possibly active sprints shared with the same project.End of the deletion
>
> Begin of the insertion End of the insertion * Begin of the insertionAllEnd of the insertion Begin of the deletion A solution might be to take away the possibility to mange sprints inEnd of the deletion projects Begin of the insertionsharing
End of the insertion Begin of the deletion that have a sprint shared with them. Because probably, it will not be the only sprint from the same source but rather, that all sprints are defined from there. 
End of the deletion > Begin of the insertion
End of the insertion Begin of the deletion So it might a setting in the project, not in the sprint, whether all of its sprints are shared. 
End of the deletion > Begin of the insertion* End of the insertion Begin of the deletion If there is a conflict between two shared sprint setting, the one closer to the project would win (Systemwide < Sub-projects <End of the deletion Subproject Begin of the insertionsharing higher upEnd of the insertion Begin of the deletion closer toEnd of the deletion the Begin of the insertionancestor chainEnd of the insertion Begin of the deletion project < project)End of the deletion
> Begin of the insertion

CopiedEnd of the insertion Begin of the deletion
>
&gt; \-- copiedEnd of the deletion from <mention class="mention" Begin of the insertiondata-id="70496"End of the insertion Begin of the deletion data-id=&quot;71242&quot;End of the deletion data-type="work_package" Begin of the insertiondata-text="###70496">###70496</mention>&nbsp;End of the insertion Begin of the deletion data-text=&quot;#71242&quot;&gt;#71242&lt;/mention&gt; [comment](https://community.openproject.org/projects/stream-jira-agile-replacement/work_packages/71242/activity#comment-1625712) End of the deletion

<br>

<br>