Sort in filters is based on Name and is not editable

I can’t reopen this: Compact Relation view not sorted by rank

But its the same concept, but in the view filters. For single and multi select its by rank, but for relations its by name.

And in view filters theres no way to edit this.

Not a huge deal, but a minor inconvenience.

Related to this too: Default Sort per Db as config option

I’m not sure I understand.
What do you mean by ‘sort in filters’?
You are talking about relation filters, right?

No, sorry. I mean the filters when making / editing a view.

Like, view filters.

So, filter settings in sidebar views, right?

I still don’t know what ‘sort in filters’ means?

Maybe a screenshot will help…

As in. It is sorted in this way and can’t be set to be any different.

In here. I guess in other view config as well like smart folder. When adding filters for single and multi select, it’s sorted by rank, but when adding filters to relationships, it’s sorted by name.


Do you mean that the list of options to choose from (for the right-hand side of a filter) is alphabetic when it is a relation field filter, but rank-ordered when it is a select field filter?

So, e.g.
Project is any of Boring job, Do this, Final thing
whereas
State is any of Open, In Progress, Done

If so, I’m not sure why this ought to be considered a bug.

I mean, I think it’s unlikely that we would implement configurability of this sort order, and therefore it has to be a hard-coded choice. And inevitably that choice can’t be ideal for every situation but …
IMHO, given the typical use cases of select fields, then rank order seems reasonable, and for relations, alphabetic by name seems reasonable.

Plus, a user can always start typing to get to the one they want.

Exactly!
Hmm. I guess this is indeed just a design choice, as it’s not configurable by the user.
My use case is using a database for “State” as we need to connect it and add rules to it. For now we could just add a number prefix for it to sort right. When there are more states, knowing which one comes first gets tricky with no rank sort.

Even more strongly relates to this then: Default Sort per Db as config option

1 Like