You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When editing group/user/role associations, an admin can choose between simple select and column select. When there are too many items to display, both select options display a reasonable number of options and offer ways to browse or search for items. However, when displaying already selected items, the simple select will display all of them, which becomes a problem if there are too many: that UI is hardly helpful. I think disabling simple select for such cases, or limiting how many records are displayed would be one way to address this.
(reduced quality of screenshot is intentional)
The text was updated successfully, but these errors were encountered:
This interface should already default to column select. The default select interface is decided based on the number of options. If it doesn't, this may be a bug.
It does use the correct component by default, but the simple select is still available as an option, so one could click it (like I did) and end up with all those selected items displayed. So, ideally, I think, there should be a threshold after which that option is no longer available (and show "too many items to display" instead?). That said, this could affect only the three big instances and only in edge cases which are rare, so it isn't really a priority. So, unless this has a quick and easy fix, we can close it.
This is a minor admin UI inconvenience.
When editing group/user/role associations, an admin can choose between simple select and column select. When there are too many items to display, both select options display a reasonable number of options and offer ways to browse or search for items. However, when displaying already selected items, the simple select will display all of them, which becomes a problem if there are too many: that UI is hardly helpful. I think disabling simple select for such cases, or limiting how many records are displayed would be one way to address this.
(reduced quality of screenshot is intentional)
The text was updated successfully, but these errors were encountered: