# Feature AGILE-219 - 1st iteration of filters within the backlog

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.9.0 |
| Sprint | Sprint 10 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| AGILE-302 | Do not carry the filter state in all the backlog urls | Implementation | closed |  | 17.7.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-434 | Bug | Backlogs: Infinite page reload loop when applying Is milestone filter | closed |  | 17.9.0 |  | Modules and project features / Backlogs |
| AGILE-432 | Bug | Backlogs: page crashes on projects with lots of work packages when filter is removed | closed |  | 17.9.0 |  | Modules and project features / Backlogs |
| AGILE-439 | Bug | Backlogs: "Shared with users" filter is not working | closed |  | 17.9.0 |  | Modules and project features / Backlogs |
| AGILE-438 | Bug | Backlogs: "Observed in versions" filter shows versions ids instead of labels | closed |  | 17.9.0 |  | Modules and project features / Backlogs |
| AGILE-437 | Bug | Backlogs: Some filters should not be present | closed | Ivana Šugić | 17.9.0 |  | Modules and project features / Backlogs |
| AGILE-435 | Bug | Backlogs: Keyboard focus shifts to Add filter instead of input field after selecting a filter | closed |  | 17.9.0 |  | Modules and project features / Backlogs |
| DREAM-738 | Code maintenance | Teach SelectPanel to support a dynamic counter | on hold |  | Product Backlog |  | Frontend components and Primer design system / Quick filter, Modules and project features / Query and filter, Frontend components and Primer design system |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Backlogs, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=4747-41874&t=k9Mpz7ZgqRSg6SKS-4 |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As** a user  
**I want to quickly** find certain wp within the backlog / sprint  
**so that** I can do my backlog refinement / sprint planning.

**As** a user  
**I want to** drill down the backlog & sprints view  
**so that** I can focus on certain parts of the view without noise

**Acceptance criteria**

  - There is a filter section on the top of the page with:
    
      - A search box ("Search by name"): filters for work packages titles matching the text input
    
      - A Filters button that displays the existing Filters panel
    
    <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921856/content">

  - The selected filters apply to the mentioned containers, and show only wp respecting the filters
    
      - sprints
    
      - backlog buckets
    
      - backlog inbox

  - The counter and the story points within the containers will be adjusted based on the visible wp
    
      - \[open\] Do we want to adjust the story points and counters completely or have it display always the total (without filtering) or display both the total as well as the filtered for number of points and counters?
    
      - *\[open\] Same for the total \#. I don't know if filtering should necessarily change that number, since a bucket or sprint does have that many items in them. Perhaps that total is important, even for users to realise that the view is filtered?*

  - "Show xyz more items" button within the backlog inbox
    
      - the number of wp should be adjusted dynamically
    
      - when I click on the more button to expand the list, I see only wp respecting the filters

  - drag\&drop behavior
    
      - positioning a wp after another one should be persisted also once the filter was removed by the user and all wp are visible again. The dropped wp should be then still right after the reference while dropping.
    
      - when dragging into a sprint/bucket that has been completely emptied out by filtering - a blankslate is shown - then the dragged in work package will be positioned at the top.

  - move actions triggered by the sprint (and later on inbox and backlog bucket) container
    
      - Same as for drag and drop, only visible elements are considered.

  - If all elements are filtered out of a container, a blankslate is displayed
    
      - The blankslate is specific to the filtering. The default (no items exist yet) slate is not used.
    
      - \[open\] phrasing 

  - The types and statuses configured in the backlog setting of the project do not affect the filters. However, ideally, the statuses and types excluded by the project settings should be indicated in the filter section. ( Will be done in a follow up <mention class="mention" data-id="79511" data-type="work_package" data-text="#AGILE-418" data-display-id="AGILE-418">\#AGILE-418</mention> )
    
      - \[open\] visuals

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - Everyone allowed to see the page can use the filters

**Translation considerations**

  - *Key terms and phrases in the key languages*

**Out of scope**

  - "save view" functionality

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*