# Feature OP-19256 - Build Primer quickfilter

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

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| OP-19274 | Build segmented control quickfilter | Implementation | closed |  | 17.5.0 |  |
| OP-19275 | Build select panel quickfilter for meeting index | Feature | closed |  | 17.6.0 |  |
| OP-19291 | Make search a quickfilter | Implementation | rejected |  | 17.5.0 |  |
| OP-19305 | Enforce order of subheader slots/quickfilters | Feature | closed |  | 17.6.0 |  |
| OP-19306 | Build icon button quickfilter | Implementation | in specification |  |  |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-19579 | Bug | Harmonize behaviour between quick filters and "All filters" | closed |  | 17.6.0 |  | Frontend components and Primer design system, Modules and project features / Meetings |
| OP-19578 | Bug | Update "All filters" button where quick filters are used | closed |  | 17.6.0 |  | Modules and project features / Meetings, Frontend components and Primer design system |
| OP-19670 | Bug | Page takes a long time to load and does not sort correctly when removing 'Start time' from 'All filters' | closed |  | 17.9.0 |  | Modules and project features / Meetings, Frontend components and Primer design system |

## Technical Details

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

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/8L1YIQi38u63Zd3amahkgP/Quick-filters?node-id=237-32035&p=f&t=pmmWL605FZzAu4ac-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | OP Dev Sirius Team |
| 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

**Visual hint**

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://community.openproject.org/api/v3/attachments/920437/content"></div></figure>

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

**Permissions and visibility considerations**

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