Content
View differences
Updated by Jens Ulferts 12 days ago
**As** an agile user
**I want** all work packages to appear in a backlog automatically
**so that** I don't have to place in there before - I can then start assigning them to a sprint or a backlog bucket from the "Sprint planning" view without detours.
**Acceptance criteria**
* There is an "Inbox" "All backlog items" default backlog bucket (Name potentially subject to change)
* It includes all items in the project that are:
* open (not rejected, not closed)
* not in another backlog bucket
* not in a sprint
* Matching the backlogs setting on what is a story (until ###71305 lifts that limitation)
* If there are more than 60 work packages matching the list:
* The top 50 work packages are displayed
* the lower 10 work packages are displayed
* the work packages in between are hidden and replaced by a text informing the user about the hidden fields.
* Clicking on the text displays all elements
* \[open\] potentially, we only display another x work packages then again informing the user that there are more. The reason for this is the expected performance impact of displaying potentially thousands of work packages.
* The work packages can be sorted manually in this bucket both via drag & drop as well as via menu entry.
* Work packages not sorted manually (yet) are placed at the bottom of the "Inbox" "All backlog items" backlog
* The sort order is thus "Manual" > "Created at"
* If a work package is created using a backlog item's menu ("Create new below"), the new work package is to be sorted below the work package the action was triggered from
* This would indicate that at this point, all work packages above need to receive a manual sort order automatically as well.
* \[open\] Potentially there will be a technical limitations that only how to sort the work packages above the "hidden work packages" fold will be sortable. that are not sorted manually yet (because they have been created elsewhere)
* <br>
**Technical notes**
* \-
**Permissions and visibility considerations**
* Changing order, removing and adding of work packages from/to No specific permission required. The user needs access to the "Inbox" backlog bucket requires the "Manage sprint items" permission. &quot;Sprint planning&quot; view.
**Translation considerations**
* \-
**Out of scope**
* Changing the position in the backlog is not visible on the work package. I.e there is no journal entry
* Everything else in <mention class="mention" data-id="71368" data-type="work_package" data-text="##71368">##71368</mention>
**I want** all work packages to appear in a backlog automatically
**so that** I don't have to place in there before - I can then start assigning them to a sprint or a backlog bucket from the "Sprint planning" view without detours.
**Acceptance criteria**
* There is an "Inbox"
* It includes all items in the project that are:
* open (not rejected, not closed)
* not in another backlog bucket
* not in a sprint
* Matching the backlogs setting on what is a story (until ###71305 lifts that limitation)
* If there are more than 60 work packages matching the list:
* The top 50 work packages are displayed
* the lower 10 work packages are displayed
* the work packages in between are hidden and replaced by a text informing the user about the hidden fields.
* Clicking on the text displays all elements
* \[open\] potentially, we only display another x work packages then again informing the user that there are more. The reason for this is the expected performance impact of displaying potentially thousands of work packages.
* The work packages can be sorted manually in this bucket both via drag & drop as well as via menu entry.
* Work packages not sorted manually (yet) are placed at the bottom of the "Inbox"
* The sort order is thus "Manual" > "Created at"
* If a work package is created using a backlog item's menu ("Create new below"), the new work package is to be sorted below the work package the action was triggered from
* This would indicate that at this point, all work packages above need to receive a manual sort order automatically as well.
* \[open\] Potentially there will be a technical limitations that only
* <br>
**Technical notes**
* \-
**Permissions and visibility considerations**
* Changing order, removing and adding of work packages from/to
**Translation considerations**
* \-
**Out of scope**
* Changing the position in the backlog is not visible on the work package. I.e there is no journal entry
* Everything else in <mention class="mention" data-id="71368" data-type="work_package" data-text="##71368">##71368</mention>