Content
View differences
Updated by Klaus Zanders about 2 months ago
**As** a user \[enter role of list views user\]
**I want to** use quick filters and primerized filter dialog \[enter objective\]
**so that** my data is filtered in a pleasant way \[enter desired result\]
<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 "all filters" 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** <br>
**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 "filter builder" 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. <br>
**Permissions and visibility considerations**
* When we do need to implement our own autocompleter controller for the SelectPanel, make sure to properly use visible scopes _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**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 "all filters" 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 "filter builder" 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
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._