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 the “orderable” option is enabled for the Tenant collection, the Tenant Selector should honor the custom order we’ve defined. In some use cases, for example, when a user manages multiple tenants that have an inherent priority (such as usage frequency), sorting purely by the useAsTitle isn’t very practical. We’d appreciate having the custom order honored whenever ‘orderable’ is enabled.
anyuj
changed the title
Tenant Selector ignores custom order when ‘orderable’ is enabled
Tenant Selector doesn’t honor the custom order when ‘orderable’ is enabled for Tenant collection
Apr 29, 2025
…able enabled for tenant collection (#12314)
### What?
Tenant Selector doesn’t honor the custom order when ‘orderable’ is
enabled for Tenant collection
### Why?
Currently, it uses "useAsTitle" to sort. In some use cases, for example,
when a user manages multiple tenants that have an inherent priority
(such as usage frequency), sorting purely by the useAsTitle isn’t very
practical.
### How?
Get "orderable" config from the tenant collection's config, if it has
"orderable" set as true, it will use _order to sort. If not, it will use
"useAsTitle" to sort as default.
Fixes#12246

Describe the Bug
When the “orderable” option is enabled for the Tenant collection, the Tenant Selector should honor the custom order we’ve defined. In some use cases, for example, when a user manages multiple tenants that have an inherent priority (such as usage frequency), sorting purely by the useAsTitle isn’t very practical. We’d appreciate having the custom order honored whenever ‘orderable’ is enabled.
Link to the code that reproduces this issue
https://github.com/anyuj/multi-tenant-plug-issue
Reproduction Steps
Which area(s) are affected? (Select all that apply)
plugin: other
Environment Info
The text was updated successfully, but these errors were encountered: