Content
View differences
Updated by Jens Ulferts 17 days ago
**As** a product owner
**I want to** group work packages into backlog buckets and prioritize them against each other
**so that** backlog refinement is possible even with a large set of work packages
**Acceptance criteria**
* Backlog buckets are lists of work packages.
* They have a user provided name.
* The "Sprint planning" view shows backlog buckets.
* The name and the number of work packages within the bucket are displayed.
* Users can sort the items in a backlog bucket via drag & drop and via menu entries.
* A work package can
* only be in a single backlog bucket at a time.
* cannot be in a backlog bucket and a sprint at the same time.
* cannot be in a backlog bucket and the "inbox" backlog bucket at the same time
* Users can move a work package into a backlog via a menu entry in
* Sprints
* "Inbox" backlog bucket
* Another backlog bucket
* The backlog buckets are ordered by name (asc). The "Inbox" backlog is always displayed at the top.
* A backlog bucket can be created on the view via the "+ Backlog bucket" on the page.
* Clicking on the button opens a modal in which the name can be inserted
* Backlog buckets can be deleted via a menu entry in the bucket menu
* Buckets can be renamed via a menu entry in the bucket menu
* A modal opens in which the user inserts the new name.
* Buckets are only present within the project in which they were created. There is no sharing of them for now.
* Upon deletion of a backlog bucket, all its work packages fall back into the inbox
* \[open\] top or bottom - probably bottom or display a modal asking the user
**Technical notes**
* Since this is a larger topic that could potentially be split into smaller chunks, it probably makes sense to develop it behind a feature flag.
**Permissions and visibility considerations**
* Creation/Deletion of buckets requires the `create_sprints` permission
* Moving a work package into/out of a bucket requires the `manage_sprint_items` permission
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* The backlog bucket a work package is in, is not visible on the work package itself. To be changed in #73887
* The backlog property is for now not part of the work packages API. There is also no other API for the buckets for now. To be changed in #73887
* For now, all backlogs are always displayed. This should later on be replaced by a (multi-)select by which the user can toggle the visibility of the backlog buckets.
* Creation of work packages inside a backlog bucket is not yet possible (subject to change)
**I want to** group work packages into backlog buckets and prioritize them against each other
**so that** backlog refinement is possible even with a large set of work packages
**Acceptance criteria**
* Backlog buckets are lists of work packages.
* They have a user provided name.
* The "Sprint planning" view shows backlog buckets.
* The name and the number of work packages within the bucket are displayed.
* Users can sort the items in a backlog bucket via drag & drop and via menu entries.
* A work package can
* only be in a single backlog bucket at a time.
* cannot be in a backlog bucket and a sprint at the same time.
* cannot be in a backlog bucket and the "inbox" backlog bucket at the same time
* Users can move a work package into a backlog via a menu entry in
* Sprints
* "Inbox" backlog bucket
* Another backlog bucket
* The backlog buckets are ordered by name (asc). The "Inbox" backlog is always displayed at the top.
* A backlog bucket can be created on the view via the "+ Backlog bucket" on the page.
* Clicking on the button opens a modal in which the name can be inserted
* Backlog buckets can be deleted via a menu entry in the bucket menu
* Buckets can be renamed via a menu entry in the bucket menu
* A modal opens in which the user inserts the new name.
* Buckets are only present within the project in which they were created. There is no sharing of them for now.
* Upon deletion of a backlog bucket, all its work packages fall back into the inbox
* \[open\] top or bottom - probably bottom or display a modal asking the user
* Since this is a larger topic that could potentially be split into smaller chunks, it probably makes sense to develop it behind a feature flag.
**Permissions and visibility considerations**
* Creation/Deletion of buckets requires the `create_sprints` permission
* Moving a work package into/out of a bucket requires the `manage_sprint_items` permission
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* The backlog bucket a work package is in, is not visible on the work package itself. To be changed in #73887
* The backlog property is for now not part of the work packages API. There is also no other API for the buckets for now. To be changed in #73887
* For now, all backlogs are always displayed. This should later on be replaced by a (multi-)select by which the user can toggle the visibility of the backlog buckets.
* Creation of work packages inside a backlog bucket is not yet possible (subject to change)