Content
View differences
Updated by Jens Ulferts about 7 hours ago
**As** an agile user
**I want to** have a central page for planning my sprints
**so that** I know where to do it and have the means to efficiently plan my sprints
**Acceptance criteria**
* Add a menu item "Sprint planning" to the "Backlog" menu
* This menu item is the default menu item for Backlog. It opens when Backlog is clicked
* This replaces the existing Backlogs page
* The backlogs are displayed to the left
* ###72198 is displayed by default
* The Potentially, the version backed backlogs are selectable from a drop down above
* In the version settings, the "Column in backlogs" select is switched to a checkbox. It reads "Use as backlog".
* Existing versions having "Column in backlogs" set to "right", have the checkbox checked.
* Since there is a feature flag in place, the database cannot be changed yet.
(see #72529)
* The backlog is restyled. See Figma.
* The sprints are displayed to the right
* Only sprints that are "In planning" or "Active" are displayed
* The sprints are ordered by dates first and then by name (ascending)
* The sprints are restyled. See Figma.
* Work packages displayed in either sprint or backlog
* show:
* In the first row
* type
* id
* status
* assignee
* story points
* priority
* In the second row
* subject
* In the third row
* parent
* have a menu
* Open details view (opens split screen)
* Open fullscreen view
* Copy url to clipboard
* Copy work package id
* Create new below
* Move
* options to move
* top
* up
* down
* bottom
* to a sprint
* This opens a modal for moving the work package to a sprint
* No filter header in the initial phase.
* There is a "+ Sprint" button that opens the sprint creation modal.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* "View sprints" required to access the page
* "Create sprints" to see the "+ Sprint" page and use it
* It will only be displayed if the project is configured to have own sprints (not receiving)
* "Manage sprint items" required to add/remove items to/from a sprint and to reorder the sprint.
* "Start/complete sprint" required to change the status of the sprint.
* Sprints that are shared with the project, cannot be edited.
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** have a central page for planning my sprints
**so that** I know where to do it and have the means to efficiently plan my sprints
**Acceptance criteria**
* Add a menu item "Sprint planning" to the "Backlog" menu
* This menu item is the default menu item for Backlog. It opens when Backlog is clicked
* This replaces the existing Backlogs page
* The backlogs are displayed to the left
* ###72198 is displayed by default
* The
* In the version settings, the "Column in backlogs" select is switched to a checkbox. It reads "Use as backlog".
* Existing versions having "Column in backlogs" set to "right", have the checkbox checked.
* Since there is a feature flag in place, the database cannot be changed yet.
* The sprints are displayed to the right
* Only sprints that are "In planning" or "Active" are displayed
* The sprints are ordered by dates first and then by name (ascending)
* The sprints are restyled. See Figma.
* Work packages displayed in either sprint or backlog
* show:
* In the first row
* type
* id
* status
* assignee
* story points
* priority
* In the second row
* subject
* In the third row
* parent
* have a menu
* Open details view (opens split screen)
* Open fullscreen view
* Copy url to clipboard
* Copy work package id
* Create new below
* Move
* options to move
* top
* up
* down
* bottom
* to a sprint
* This opens a modal for moving the work package to a sprint
* No filter header in the initial phase.
* There is a "+ Sprint" button that opens the sprint creation modal.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* "View sprints" required to access the page
* "Create sprints" to see the "+ Sprint" page and use it
* It will only be displayed if the project is configured to have own sprints (not receiving)
* "Manage sprint items" required to add/remove items to/from a sprint and to reorder the sprint.
* "Start/complete sprint" required to change the status of the sprint.
* Sprints that are shared with the project, cannot be edited.
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._