- in total, there are two types of filters:
- input fields
- user input with auto-suggestion for the input
- once clicked, a dialogue opens with 10 suggested terms, each with a checkbox
- the checkboxes can be selected and the respective term can be added to selected filters via a "apply" button
- dropdown fields
- if the amount of terms the user can select is rather small, a dropdown menu can be used instead of an input field
- input fields
Elements
ID | Title | Show? | Action | Changes | Tickets |
| 1 | filter header | always | clicking on it closes the filter box | ||
| 1a | amount of filters | when a min. of 1 filter is selected | (de-)selecting filters changes the number | ||
| 2 | reset all filters | when more than one filter was selected | all filters can be removed, which leads to the content on the page adapting | ||
| 3 | filter areas | always | filters can be selected and are shown below the respective category | / | |
| 3a | input filters | always | user types a term into the field, a group of terms are displayed based on the input | no more placeholder text | DDBNEXT-6382 - Getting issue details... STATUS |
| 3b | dropdown filters | always | user opens a dropdown menu with a set amount of results from which the user can select | / | |
| 3c | time filter | always | / | / | DDBNEXT-6517 - Getting issue details... STATUS |
| 4 | selected filters | when filters were selected | filter can be removed, which leads to the content on the page adapting | DDBNEXT-6381 - Getting issue details... STATUS | |
| 5 | dropdown menu | when user interacts with a filter |
Other Changes
- implementation:
- DDBNEXT-6380 - Getting issue details... STATUS
- responsive view:
- DDBNEXT-6522 - Getting issue details... STATUS
- bottom of module:
- DDBNEXT-6523 - Getting issue details... STATUS
- behavior:
- DDBNEXT-6518 - Getting issue details... STATUS