Content
View differences
Updated by Jens Ulferts about 2 months 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 The setting for"task type" is removed from being shown on the "backlogs and sprints" page. backlog admin settings
* Within "Project settings" -> "backlogs" "Story types" setting will be reworked
* A new tab is added called "Types" Renaming the setting to "Work package types automatically visible in the backlog"
* There is a field called "Excluded types"
* The field has a caption explaining what it does.
* \[open\] Phrasing
* Per default, when setting up a project all work package types should be set as active. Except if the field is empty.
* Upon copying a project (e.g., because it is a template) template defines something else, then we should take over the values are copied as well.
settings from the project template.
* Using a multi select autocompleter, the project admin Project admins can select any set of deactivate work package types currently active in order to remove them from the project automated backlog
* This includes selecting all work package types. We don't protect from this non-sensical selection.
* Work packages of types selected in the blocklist:
* this type will not be displayed in automatically removed from the inbox backlog nor and backlog buckets.
* will be displayed In case wp of this type are in active sprints we should not remove them from sprints.
* We should warn a user that the WP wp won't be removed from active sprints. (TBD)
* \[open\] will we warn the project administrator while they In case wp of this type are changing the setting? Or is the warning displayed when viewing the "backlogs and sprints" page?
* will not be displayed in sprints that sprints, which are in planning
* We we should warn the user that the WP wp will be removed from those sprints.
* \[open\] same as above
While creating new work package types "Display in backlog per default" checkbox appears and is set to active per default. Admin would need to actively deactivate it if needed.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918624/content">
* \[open\] If we show it for Work packages of all active but not for planned sprints, WPs might backlog types can be associated to sprints
* Work packages associated to a sprint show up from hiding when in the sprint is turned active. And they will hide again when moving unfinished WPs on and the blocklist to the inbox or next planned sprint.
sprint's board regardless of their type
* \[open\] The modal for creating new All work packages in a project matching the sprints (and potentially the backlogs once that is implemented) only shows the work package types active backlog filter show up in the project that are not blocked. The necessity of this depends on whether we hide/show blocked WP types in all sprints. backlog
**Technical notes**
* <br>
**Permissions and visibility considerations**
* \[open\] Which permission is necessary for No changes
**Translation considerations**
* _Key terms and phrases in the administration? key languages_
**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 <br>
_Set the_ **To be informed/consulted teams** _field to add include all teams necessary to be informed of the "sprint" and "story point" field independently. changes._
**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
* Within "Project settings" -> "backlogs"
* A new tab is added called "Types"
* There is a field called "Excluded types"
* The field has a caption explaining what it does.
* \[open\] Phrasing
* Per default, when setting up a project
* Upon copying a project (e.g., because it is a template)
* This includes selecting all work package types. We don't protect from this non-sensical selection.
* Work packages of types selected in the blocklist:
*
* We should warn a user that the WP
* will not be displayed in sprints that
* We
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918624/content">
* Work packages associated to a sprint
* <br>
* \[open\] Which permission is necessary for
**Translation considerations**
* _Key terms and phrases in
**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
_Set the_ **To be informed/consulted teams** _field