Bug #7737
closed
An abuse group is (wrongly) autoselected when creating new filter
Added by Radko Krkoš 4 months ago.
Updated 3 months ago.
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.
- Status changed from New to In Progress
- Assignee set to Jakub Judiny
- 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).
- Target version changed from Backlog to Future
- Assignee set to Rajmund Hruška
- Target version changed from Future to 2.13
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.
- Status changed from In Progress to Resolved
- Related to Task #7751: Replace QuerySelectMultipleField by wtforms.SelectMultipleField added
- Status changed from Resolved to In Review
- Status changed from In Review to Closed
Also available in: Atom
PDF