Bug #7737
closedAn abuse group is (wrongly) autoselected when creating new filter
0%
Description
When creating new filter, the group selector has a default value - the first item on the list. That does not make much sense in case someone may manage several groups, especially for administrators and maintainers, who can manage all groups. Nothing selected seems like a better option.
Related issues
Updated by Jakub Judiny 4 months ago
- Status changed from New to In Progress
- Assignee set to Jakub Judiny
Updated by Jakub Judiny 4 months ago
- Assignee deleted (
Jakub Judiny)
This will not be possible to do because of issues we have with TomSelect. If it will be empty from the start, it will still look like something is selected and user will still have to manually remove it. So the current state is much better (for most users).
Updated by Jakub Judiny 4 months ago
- Related to Support #7673: Replace bootstrap-selectpicker added
Updated by Jakub Judiny 4 months ago
- Target version changed from Backlog to Future
Updated by Rajmund Hruška 3 months ago
- Assignee set to Rajmund Hruška
- Target version changed from Future to 2.13
Updated by Rajmund Hruška 3 months ago
Jakub Judiny wrote in #note-2:
This will not be possible to do because of issues we have with TomSelect. If it will be empty from the start, it will still look like something is selected and user will still have to manually remove it. So the current state is much better (for most users).
I think it is actually possible by using wtforms.SelectField instead of wtforms_sqlalchemy.QuerySelectField and a bit of refactoring. And we can get rid of the option Nothing selected being selected in GUI in that fields.
Updated by Rajmund Hruška 3 months ago
- Status changed from In Progress to Resolved
Updated by Rajmund Hruška 3 months ago
- Related to Task #7751: Replace QuerySelectMultipleField by wtforms.SelectMultipleField added
Updated by Rajmund Hruška 3 months ago
- Status changed from Resolved to In Review