Content
View differences
Updated by Rosanna Sibora 11 days 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**
* The setting for"task type" is removed from backlog admin settings
* "Story types" setting will be reworked
* Renaming the setting to "Work package types automatically visible in the backlog"
* Per default, when setting up a project all work package types should be set as active. Except if the project template defines something else, then we should take over the settings from the project template.
* Project admins can deactivate work package types in order to remove them from the automated backlog
* Work packages of this type will be automatically removed from the backlog for stories and backlog buckets.
* 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 won't be removed from active sprints. (TBD)
* In case wp of this type are in sprints, which are in planning we should warn the user that the wp will be removed from those sprints.
* 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.
removed
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918624/content">
* Work packages of all active backlog types can be associated to sprints
* Work packages associated to a sprint show up in the sprint and the sprint's board regardless of their type
* All work packages in a project matching the backlog filter show up in the backlog regardless of their type
**Technical notes**
* <br>
**Permissions and visibility considerations**
* No changes
**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 work packages of all types show up in backlogs (sprints, backlog and board)
**so that** I am not limited by the system
**Acceptance criteria**
* The setting for"task type" is removed from backlog admin settings
* "Story types" setting will be reworked
* Renaming the setting to "Work package types automatically visible in the backlog"
* Per default, when setting up a project all work package types should be set as active. Except if the project template defines something else, then we should take over the settings from the project template.
* Project admins can deactivate work package types in order to remove them from the automated backlog
* Work packages of this type will be automatically removed from the backlog
* 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 won't be removed from active sprints. (TBD)
* In case wp of this type are in sprints, which are in planning we should warn the user that the wp will be removed from those sprints.
* 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.
* Work packages of all active backlog types can be associated to sprints
* Work packages associated to a sprint show up in the sprint and the sprint's board regardless of their type
* All work packages in a project matching the backlog filter show up in the backlog
**Technical notes**
* <br>
**Permissions and visibility considerations**
* No changes
**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._