Content
View differences
Updated by Parimal Satyal 3 days ago
**As** an agile user
**I want to** activate multiple sprints at the same time
**so that** multiple teams can work within the same project at the same time
#### **Acceptance criteria**
* **If If configured for the project, multiple sprints can be activated at the same time.** time.
* There is no limit to how many sprints can be activated
* The functionality for activating sprints is unchanged, i.e. a board is created when activating and the status is changed.
* Within the project administration of backlogs, a user can configure to have multiple active sprints in the project.
* **In project settings,**
* Rename "Backlogs" to "Backlog and sprints"
* Rename "Sprint sharing" tab to "Sprints"
* Add a Activating the setting to enable/disable multiple active sprints.
* This will be a block titled 'Number of active sprints' after the sharing options with two radio options:
* Single active sprint
* Multiple active sprints
* These options will is only be available when 'Don't share' is selected in the 'Sprint sharing' section above.
* If any other option selected (i.e, the project is sharing is receiving sprints), the options are not visible. Instead, an [InlineMessage](https://primer.style/product/components/inline-message/#tone-variants) (scheme: unavailable) informs the user that multiple active sprints are not available when possible if sprint sharing or receiving is enabled.
set to "Don't share"
* If multiple active sprints is enabled, the project no longer has the limitation of having just one sprint marked as active at any given time. It can have multiple sprints active in parallel.
* Activating the setting disables the possibility to change the sharing settings
* If there are currently multiple active sprints running, the setting cannot be changed
<br>
**Technical notes**
<br>
* <br>
**Permissions and visibility considerations**
* \[open\] permission necessary for configuring using multiple active sprints in the project - "Share sprint"? sprint"?
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Sharing sprints and multiple active sprints active at the same time within the project
* Reporting functionality that requires knowing the continuity of sprints,
* e.g. all those belonging to "Team A" to calculate a velocity chart
* Assigning a sprint to a team
* Changes to the close sprint functionality
**I want to** activate multiple sprints at the same time
**so that** multiple teams can work within the same project at the same time
#### **Acceptance criteria**
* **If
* There is no limit to how many sprints can be activated
* The functionality for activating sprints is unchanged, i.e. a board is created when activating and the status is changed.
* Within the project administration of backlogs, a user can configure to have multiple active sprints in the project.
* **In project settings,**
* Rename "Backlogs" to "Backlog and sprints"
* Rename "Sprint sharing" tab to "Sprints"
* Add a
* This will be a block titled 'Number of active sprints' after the sharing options with two radio options:
* Single active sprint
* Multiple active sprints
* These options will
* If any other option selected (i.e, the project is sharing is receiving sprints), the options are not visible. Instead, an [InlineMessage](https://primer.style/product/components/inline-message/#tone-variants) (scheme: unavailable) informs the user that multiple active sprints are not available when
* Activating the setting disables the possibility to change the sharing settings
* If there are currently multiple active sprints running, the setting cannot be changed
<br>
<br>
* <br>
**Permissions and visibility considerations**
* \[open\] permission necessary for configuring using multiple active sprints in the project - "Share sprint"?
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Sharing sprints and multiple active sprints active at the same time within the project
* Reporting functionality that requires knowing the continuity of sprints,
* e.g. all those belonging to "Team A" to calculate a velocity chart
* Assigning a sprint to a team
* Changes to the close sprint functionality