Content
View differences
Updated by Rosanna Sibora about 1 month ago
**As** a backlog user
**I want to** have work packages of all types show up in backlogs (sprints, backlog and board)
**so that** I am not limited by the system
**Acceptance criteria**
* Work package of selected types can be excluded from being shown on the "backlogs and sprints" page.
* Within "Project settings" -> "backlogs"
* Change the "Done status" tab title to "Types and Statuses"
* Rename "Definition of Done" to \[open\]
* "Addititionally closed status" / "Completed status"
* "Statuses considered mapped to completed"
* "Statuses mapped to closed"
+1
* "Closed statuses"
* Rework caption \[open\] wording
_Choose the statuses that represent a closed or finished state in your workflow. These will be treated as the "Closed" state across reporting (e.g. burndown), filters, and automations. For example, statuses like Done, Resolved, or Won't Fix may all represent a closed work item in your process._
* Always show statuses having the meta status closed as non removable items in the list to indicate, that they will always be excluded.
* There is a field called "Excluded work package types"
* The field has a caption explaining what it does.
* \[open\] _Choose which work package types to hide from Choose the backlog. Items of the selected types will not appear automatically, keeping your backlog focused on the work statuses that matters to represent a closed or finished state in your team. workflow. For example types example, statuses like Epics _Done_, _Resolved_, or Milestones that are managed at _Won't Fix_ may all represent a higher level can closed work item in your process. Any work item reaching one of these statuses will be hidden to keep considered closed by the backlog focused on actionable items._ system.
* Per default, when setting up a project the field is empty.
* Upon copying a project (e.g., because it is a template) the values are copied as well.
* Using a multi select autocompleter, the project admin can select any set of types currently active in the project
* This includes selecting all work package types. We don't protect from this non-sensical selection.
* Work packages of types selected in the blocklist:
* will not be displayed in the inbox backlog nor backlog buckets.
* will be displayed in all sprints.
* We accept that work packages when being moved to the backlog disappear
* Show a success notification upon moving the work packages that explain that it was moved successfully but that the type is excluded which is why it is no longer displayed. \[open \] wording
* The modal for creating new work packages in the sprints (and potentially the backlogs once that is implemented) only shows the work package types active in the project that are not excluded via the setting.
* \[Technical note\] This will require implementing a backlog specific wp create modal.
**Permissions and visibility considerations**
* Rename "Select done statuses" permission to "Select backlog types and statuses"
* Add caption explaining the capabilities on the roles administration page
**Out of scope**
* The setting has no effect on which types are displayed in the sprint board.
* The setting has no effect on the type's form configuration. An administrator will have to add the "sprint" and "story point" field independently.
**I want to** have work packages of all types show up in backlogs (sprints, backlog and board)
**so that** I am not limited by the system
**Acceptance criteria**
* Work package of selected types can be excluded from being shown on the "backlogs and sprints" page.
* Within "Project settings" -> "backlogs"
* Change the "Done status" tab title to "Types and Statuses"
* Rename "Definition of Done" to
* "Addititionally closed status" / "Completed status"
*
* "Statuses mapped to
*
_Choose the statuses that represent a closed or finished state in your workflow. These will be treated as the "Closed" state across reporting (e.g. burndown), filters, and automations. For example, statuses like Done, Resolved, or Won't Fix may all represent a closed work item in your process._
* The field has a caption explaining what it does.
* \[open\] _Choose which work package types to hide from
* Per default, when setting up a project the field is empty.
* Upon copying a project (e.g., because it is a template) the values are copied as well.
* Using a multi select autocompleter, the project admin can select any set of types currently active in the project
* This includes selecting all work package types. We don't protect from this non-sensical selection.
* Work packages of types selected in the blocklist:
* will not be displayed in the inbox backlog nor backlog buckets.
* will be displayed in all sprints.
* We accept that work packages when being moved to the backlog disappear
* Show a success notification upon moving the work packages that explain that it was moved successfully but that the type is excluded which is why it is no longer displayed. \[open \] wording
* The modal for creating new work packages in the sprints (and potentially the backlogs once that is implemented) only shows the work package types active in the project that are not excluded via the setting.
* \[Technical note\] This will require implementing a backlog specific wp create modal.
**Permissions and visibility considerations**
* Rename "Select done statuses" permission to "Select backlog types and statuses"
* Add caption explaining the capabilities on the roles administration page
**Out of scope**
* The setting has no effect on which types are displayed in the sprint board.
* The setting has no effect on the type's form configuration. An administrator will have to add the "sprint" and "story point" field independently.