# Feature AGILE-70 - "Inbox" backlog bucket

Project: Stream agile
Status: closed
URL: https://community.openproject.org/work_packages/AGILE-70

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 17.3.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| AGILE-76 | What is the sort order of the work packages not ordered manually in the default all items backlog | decided |  |

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-157 | Bug | Blankslates are misaligned, have incorrect icons | closed |  | 17.3.0 |  |  |
| AGILE-156 | Bug | Work package details view squashes the main content | closed |  | 17.3.0 |  |  |
| AGILE-155 | Bug | Missing divider in Sprint menu, wrong board item label | closed |  | 17.3.0 |  | Modules and project features / Backlogs, Frontend components and Primer design system |
| AGILE-153 | Bug | Inbox - Sprints divider does not take up full height | closed |  | 17.3.0 |  | Frontend components and Primer design system, Modules and project features / Backlogs |
| AGILE-147 | Bug | Inbox counter should show rounded numbers | closed |  | 17.3.0 |  | Frontend components and Primer design system, Modules and project features / Backlogs |
| AGILE-146 | Bug | Inbox counter is misaligned | closed |  | 17.3.0 |  | Modules and project features / Backlogs, Frontend components and Primer design system |
| AGILE-145 | Code maintenance | Missing feature specs on drag & drop | closed |  | 17.3.0 |  |  |
| AGILE-142 | Bug | Moving an item via the move menu throws a 404 | closed |  | 17.3.0 |  |  |
| AGILE-141 | Bug | Inbox and sprints not on same height | closed |  | 17.3.0 |  | Modules and project features / Backlogs, Frontend components and Primer design system |
| AGILE-160 | Bug | Remove "Move to sprint" dialog divider | rejected | Attila Dombi | 17.3.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Attila Dombi |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**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" 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 (might not exist yet when the feature is written)
        
          - not in a sprint
        
          - ~~Matching the backlogs setting on what is a story~~ (<mention class="mention" data-id="71305" data-type="work_package" data-text="###71305">###71305</mention> 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" backlog. This can happen when a work package is created outside of backlogs or using the "New Story" menu item on the "Inbox" 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.~~
            
              - Not implemented yet

**Technical notes**

  - \-

**Permissions and visibility considerations**

  - Changing order, removing and adding of work packages from/to the "Inbox" backlog bucket requires the "Manage sprint items" permission.

**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>