Content
View differences
Updated by Jens Ulferts about 19 hours ago
**As** an agile user
**I want to** close a sprint and have the unfinished work packages moved to another place in bulk
**so that** it is easy to open the next sprint
**Acceptance criteria**
* An active sprint can be closed. For active sprints
* a "complete sprint" button is visible on the board
* a "complete sprint" button is visible on the sprint.
* the button replaces the start button
* Upon closing, if there are non closed (meta status) work packages in the sprint, a modal is opened.
* Giving the user the option to:
* Move them to the top of the inbox backlog
* The order is kept ideally. This is not a MUST.
* Move them to the bottom of the inbox backlog
* The order doesn't need to be kept.
* Move them to another sprint
* If this option is selected, a select is displayed by which the user can choose between the "in planning" sprints within the project. The list is limited to just the shared sprints, not those that might have been there in a project before receiving was enabled.
* They are added to the top of the moved to sprint
* Ideally, the order is kept. This is not a MUST.
* If in a project that used to have own sprints and now receives from a project, there are work packages associated to the now orphaned sprint that is to be closed, the work packages are moved as well. Doing that adds a sprint previously not shared to be shared now (because there are work packages in there now)
* If the sprint is shared, informing the user that that the choice will have an effect in the shared with sprints.
* Any user able to start/sprint in the "original" project (sprint sharer) is able to do it in any project with which it is shared. Permission to "start/stop sprint".
* Open:
* Since the user mightn't be aware that closing a sprint closes it everywhere; come up with updated text for shared sprints to make this clearer. (So this can be a variation of the current modal, just different text). Parimal will add a comment the feature or directly update the specs (Figma optional).
**Permissions and visibility considerations**
* The button is only displayed if the user has the `start_stop_sprint` permission
**I want to** close a sprint and have the unfinished work packages moved to another place in bulk
**so that** it is easy to open the next sprint
**Acceptance criteria**
* An active sprint can be closed. For active sprints
* a "complete sprint" button is visible on the board
* a "complete sprint" button is visible on the sprint.
* the button replaces the start button
* Upon closing, if there are non closed (meta status) work packages in the sprint, a modal is opened.
* Giving the user the option to:
* Move them to the top of the inbox backlog
* The order is kept ideally. This is not a MUST.
* Move them to the bottom of the inbox backlog
* The order doesn't need to be kept.
* Move them to another sprint
* If this option is selected, a select is displayed by which the user can choose between the "in planning" sprints within the project. The list is limited to just the shared sprints, not those that might have been there in a project before receiving was enabled.
* They are added to the top of the moved to sprint
* Ideally, the order is kept. This is not a MUST.
* If in a project that used to have own sprints and now receives from a project, there are work packages associated to the now orphaned sprint that is to be closed, the work packages are moved as well. Doing that adds a sprint previously not shared to be shared now (because there are work packages in there now)
* If the sprint is shared, informing the user that that the choice will have an effect in the shared with sprints.
* Any user able to start/sprint in the "original" project (sprint sharer) is able to do it in any project with which it is shared. Permission to "start/stop sprint".
* Open:
* Since the user mightn't be aware that closing a sprint closes it everywhere; come up with updated text for shared sprints to make this clearer. (So this can be a variation of the current modal, just different text). Parimal will add a comment the feature or directly update the specs (Figma optional).
**Permissions and visibility considerations**
* The button is only displayed if the user has the `start_stop_sprint` permission