-
Notifications
You must be signed in to change notification settings - Fork 161
Filtering per column
Provide filtering per column and correspoding user interface.
Elaborate more on the multi-facetted use cases
As a citizen developer, I want:
- Story 1: to be able to provide filtering per colunm, so that the users can operate with the data in the grid.
- Story 2: …, so that I can…
- Story 3: …, so that I can…
As an end user, I want:
As an user, I want to
-
have a filtering UI, so that I can filter with it.
-
access that UI from the header icon corresponding to the column I want to filter.
-
have a one condition UI, so that I can filter only by one condition.
-
have immediate or on selection filtering depending on my needs.
-
have default conditions applied, so that I can filter faster.
-
have conditions to choose from, so that I can make a more precise filtering depending on my needs.
-
have the input on focus, if there is an input to а chosen condition, so that I can make an input right away.
-
be able to quickly clear the input, using a clear icon in the input.
-
have a reset button that resets the filter, so that I can quickly reset it.
-
have a reset button inactive when there is no filter applied, so I would no there is no filter applied.
-
to have a close button so that I can close it without clicking outside the toggle.
-
Want to have an UI with two conditions, so that I can make a more complicated filtering.
-
Have a non selected exclusive AND / OR toggle options between the conditions to add a new condition.
-
Have the second condition displayed when I choose AND/OR, so that I will use it only if I need to. Changing the AND or OR changes the statement.
-
have on selection filtering, so that the data will be filtered when a choose all filtering details.
-
having Reset Button so that I can reset all conditions at once.
-
have a Reset button inactive when there is no filter applied, so I would know there is no filter applied.
-
have a Filter button that becomes active only when there is a filter applies.
-
Have the second condition removed if I deselect the toggle buttons.
Must-have before we can consider the feature a sprint candidate
...
Describe behavior, design, look and feel of the implemented feature. Always include visual mock-up
3.1. End User Experience
3.2. Developer Experience
3.3. Globalization/Localization
Describe any special localization requirements such as the number of localizable strings, regional formats
3.4. User Interface
Include a diagram linking the elements with the visual representation of the feature
3.5. Navigation
3.6. API
| Name | Description | Type | Default value | Valid values |
|---|---|---|---|---|
| Name | Description | Return type | Parameters |
|---|---|---|---|
| Name | Description | Cancelable | Parameters |
|---|---|---|---|
Specify only if applicable
| Assumptions | Limitation Notes |
|---|---|
Specify all referenced external sources