Bug #44238
open
mgr/dashboard: new table filters: lack of persistence for new filters
Added by Ernesto Puerta about 4 years ago.
Updated about 3 years ago.
Description
The new table filters are a great addition. However, the filters selected are not persisted as they previously were (and unlike other table elements, like the table sorting, 'Displayed Columns' or '# of Displayed Rows'). As the current filters require more clicks compared to the previous approach (multiple input text fields), UX would be degraded if the user cannot keep their current filter selections.
Files
Related issues
1 (1 open — 0 closed)
Are you using Firefox? This doesn't happen to me in Chrome.
- Regression changed from No to Yes
- Severity changed from 3 - minor to 2 - major
Thanks for the report. Marking this as a regression and increasing severity - this sounds like something we should fix before the initial octopus release.
- Subject changed from mgr/dashboard: new table filters: UI/UX issues to mgr/dashboard: new table filters: lack of persistence for new filters
- Description updated (diff)
@Tiago:
Thanks for the feedback! My bad, the UI part (overlapping chevron) is caused by my refactoring of the nav-menu, as some outer CSS is now propagating inside (via ::ng-deep) and affecting that.
I'll remove the UI issue and keep just the UX (lack of persistency for the new filters). Sorry for the noise.
@Lenz Grimmer, give the above, not sure if the severity still ranks as major (only the persistence misbehaviour needs a fix).
- Severity changed from 2 - major to 3 - minor
Thanks for the feedback - updating the severity accordingly.
- Related to Feature #36716: mgr/dashboard: Cluster configuration doesn't remember filters added
- Project changed from mgr to Dashboard
- Category changed from 165 to UI
Also available in: Atom
PDF
