Sorting tag type relations does not work in sets

Describe the bug
Setting a sort rule in set view for a tag type relation fails to order the objects correctly. When I add an object with a tag starting with “N”, and one with a tag starting with “C” the first object (with the “N”) will be ordered before the “C” tags. Interestingly, having more varied tags will order correctly, except for the tags starting with “N”.

To Reproduce

  1. Create a custom type.
  2. Add a new custom, tag type relation.
  3. Create 2 objects: the first with a tag starting with “N” and the other one with a tag starting with “C”.
  4. Create a set of that type.
  5. Add a sorting rule to sort the objects by that tag relation in ascending order.

Expected behavior
The objects should be in ascending order.

System Information:

  • OS: Windows 10
  • Anytype Version: 0.21.9

@gcsapo Thank you for your notice! We haven’t implemented this yet, but plan to do that in the future

1 Like

Can you please check if this is the same as the one reported here?

No, but it is similar. It seems that in my case Anytype orders the set based on the order of the options added to that tag relation, disregarding the alphabetical order.