Sorting set by tag orders objects incorrectly

Hello!
*This bug report is related to this feature request.

The Bug
When ordering a set by a tag, Anytype orders objects based on the order of the tag’s options.
For some reason, the first tag option (index 0) is always ordered last.


In the image above, “500” is the first option, but comes last in the order.

To Reproduce

  1. Create a tag relation
  2. Enable this relation within a set
  3. Ensure the relation has more than one option.
  4. Assign relational values (options) to some objects within the set
  5. Sort the set by the relation
    The first tag option, should show up last (or first if the sort is descending).

Expected Behavior
I expect the set to be ordered, in the order of the tag options.
(Or, in other words, for the first tag option to be first in the order).

System Information:
OS: Microsoft Windows 10 Home (Version 10.0.19042)
Anytype Version 0.21.5

Additional Context
N/A

Thank you for reading, hope you have an amazing day!

3 Likes
  • Shouldn’t the tags be sorted alphabetically?
  • Instead of Ascending / Descending, Would a custom sort order for tags in the sort pop-up suffice? Which would then display the draggable options such as in your feature request

Custom sort for tags is important, but few situations might require the normal sort by tag value. So it might be great if both the options are available :grinning_face_with_smiling_eyes:


Isn’t the In this object a mere suggestion to the user and does not represent any ordering? This is not the case now, as they seem to be considered for the sort from your bug report, but ideally isn’t this how they are supposed to be, just a suggestion to the user? :thinking:

1 Like
  • Shouldn’t the tags be sorted alphabetically?

In other applications (e.g. ClickUp), they’re (by default) sorted by date created — but yes, alphabetical sorting (or at least the option for this) would make a lot of sense!

Custom sort for tags is important, but few situations might require the normal sort by tag value. So it might be great if both the options are available :grinning_face_with_smiling_eyes:

Agreed!

Isn’t the In this object a mere suggestion to the user and does not represent any ordering? This is not the case now, as they seem to be considered for the sort from your bug report, but ideally isn’t this how they are supposed to be, just a suggestion to the user? :thinking:

In many other applications, sorting is based on the order of the tag options, so I assume/d this was intentional. :sweat_smile:

1 Like

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

1 Like

Thank you!

So the issue with the first tag appearing last, is intentional?

@sahilstudio
As said by Kirill_Lem, this just isn’t implemented yet and you already made a feature request for the feature that would fix this.
I don’t see the need right now for this bug report anymore. Would you be okay with closing this?

1 Like

Thank you, but this topic is in regard to a currently occurring bug, not the requested feature (but the two are related).

The feature request is to have the order of all of the Tag options be arrangeable.

This report states that, when a set is sorted by a Tag (meaning the sorting occurs based on the order of the tag options), the first Tag option (position 1) always appears last (position 5 in the example above).

1 Like

Got it, thanks for making that clear.

1 Like