# Feature OP-19198 - Build Primer Quickfilter & Filter Modal component

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-19198

## Planning

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

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| OP-19242 | Is the modal dialog the right pattern for all filters? | decided | We will only primerize the filters, not put them inside a dialog |

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| OP-19240 | Primerize advanced filters component | Feature | closed |  | 17.6.0 |  |
| OP-19256 | Build Primer quickfilter | Feature | closed | OP Dev Sirius Team | 17.7.0 |  |

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | OP Dev Sirius Team |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a user of list views  
**I want to** use quick filters and primerized filter dialog  
**so that** my data is filtered in a pleasant way

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920437/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920436/content">

<br>

**Acceptance criteria**

*   In the Subheader we allow several buttons directly as quick filters.
    
*   Those should be connected to a filter and an operation. For example when we have a users quickfilter that should map to the user\_id filter with an OR operator
    
*   An &quot;all filters&quot; button should also be added that opens a modal that offers all filters for the given query
    
*   Applying the filter in the modal sets the filters in the URL and reloads the page/frame/stream (whatever is used in the page)
    
*   For a PoC of the usage of this new component, we use the **Meetings Page**
    

**Technical notes**

*   Currently the [`with_filter_component`](https://qa.openproject-edge.com/lookbook/inspect/primer/open_project/sub_header/custom_filter_button) slot is the only possibility. We might be introducing better ways to introduce quick filters. Get in touch with the P-Team.
    
*   For quick filters like users or other things that are autocompleters we want to use the [SelectPanel](https://qa.openproject-edge.com/lookbook/inspect/primer/alpha/select_panel/playground). We have to investigate if we need to build custom controllers to respond to those queries or if we can use our APIv3
    
*   It would be **super duper great** if the &quot;filter builder&quot; in the modal content woild be implemented in a way so that it could be integrated into other primer forms. As with the screenshots above, you can see that for Resource mgmt we want to use this in other views as well. So would be great to build this re-usable from the get-go.
    

**Permissions and visibility considerations**

*   When we do need to implement our own autocompleter controller for the SelectPanel, make sure to properly use visible scopes
    

**Translation considerations**

*   _Key terms and phrases in the key languages_
