Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Refactor] Improve filter UX in Data Node/Scenario Selector #1403

Open
1 of 2 tasks
FlorianJacta opened this issue Jun 12, 2024 · 0 comments
Open
1 of 2 tasks

[Refactor] Improve filter UX in Data Node/Scenario Selector #1403

FlorianJacta opened this issue Jun 12, 2024 · 0 comments
Labels
🖰 GUI Related to GUI 📈 Improvement Improvement of a feature. 🟨 Priority: Medium Not blocking but should be addressed

Comments

@FlorianJacta
Copy link
Member

Description

The UX of creating filters could be better in the Data Node/Scenario selector. It would be better to propose something like this:

  • when the filter is on a boolean to have a switch: this simplifies the process of creating a boolean filter immensely,
  • when the filter is on a date to have date/time picker.

Providing a default "action" for each filter would enhance the filter UX. For example, the tags filter could have as a default action: "contains". Right now, you need a lot of clicks to get the filter in place.

Code of Conduct

  • I have checked the existing issues.
  • I am willing to work on this issue (optional)
@FlorianJacta FlorianJacta added 📈 Improvement Improvement of a feature. 🖰 GUI Related to GUI 🟨 Priority: Medium Not blocking but should be addressed labels Jun 12, 2024
@FlorianJacta FlorianJacta changed the title [Refactor] Improve filter UX for Data Node/Scenario Selector [Refactor] Improve filter UX in Data Node/Scenario Selector Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖰 GUI Related to GUI 📈 Improvement Improvement of a feature. 🟨 Priority: Medium Not blocking but should be addressed
Projects
None yet
Development

No branches or pull requests

1 participant