Manual sort in collections interferes with regular sort

[Code-Jack]

What’s The Bug?

It is possible to vertically move the items in the grid by hand.
But doing so distorts the sorting order permanently!

How To Reproduce It

1. Go in a Collection’s Grid.
2. Add the Relation “Last modified date”. Sort the Grid for this date.
3. Hover the mouse over an item in the Grid. A gripper appears on the left side of the line.
4. Use the gripper to move one of the items in the Grid up or down.
   Change the places where the items belong (according to their date).

You can even close and restart the app, but the sorting order stays wrong.

Only way I found to apply the correct order again:

1. Sort for another Relation.
2. Now sort again for “Last modified date”.
   It works not without the first of the two steps above.

Image or Video

The Expected Behavior

Off course, one could sell it as a “feature”, not a bug. But it is strange.
Even if you call it a “feature” the order shouldn’t stay permanently if the configuration in Sorts clearly says that the items are sorted for the date.

Additional Context:

The bug implies that there is some kind of a “Sorting Date” already under the bonnet.
See my FR for such a feature:

Custom Sort Date Relation to override Creation Date

WHAT DO YOU RECOMMEND Surely we all know the problem: sometimes it would become handy (or there is even urgent need) to change the Creation Date of an Object. There was FRs and some moanings from the users, that this isn’t possible (for some technical reasons, as far as I understand). But I have an idea! HOW COULD IT BE DONE My idea: Please implement a new “Sorting Date” Relation that is automatically available for each Objekt. Normally there is no need for the user to pay attention or to…

Device

Desktop PC

OS

Win 10

Anytype Version

v0.37.15-beta

Technical Information

OS version: win32 x64 10.0.19045
App version: 0.37.15-beta
Build number: build on 2024-01-19 23:39:59 +0000 UTC at #e31052fa0db4ae7b78981fcd8c59016aa4cd6caf (dirty)
Library version: v0.30.11
Anytype Identity: AAtt6aReARByswg2CbvZhveoJEEcnydfDu7U2VAkgJALsE7D
Analytics ID: 8a514008-4f5d-40d3-970f-a0d241b63af2
Device ID: 12D3KooWGqd6JSafCCcEwvnke5JAVgBNnuR9gGQeSBQ5HdUboWtG

[Humain]

I don’t think this is normal. Are you suggesting that manual item reordering should automatically delete the previously defined Sort parameter?

I think it could be highlighted in red in the Sorts menu, with a Reload button placed before the icon. Clicking on the icon would reset the Collection with this Sorting.

[Code-Jack]

1. I think a manual item reordering shouldn’t be possible if there is a sorting order defined.

2. In case the user wants to reorder in a very special way, he could add a relation (e.g. a number) and then sort for it.

3. But I also strongly wish the feature from my linked FR!
   This feature would spare us the need to integrate some kind of an “event date” into each Object and the need to choose a date for each of these Objects (wich is mostly identically to the Creation Date).

[Humain]

I think what Notion is proposing could be a good start, a modal that appears in the centre of the screen.

About your FR, we all want one feature more than another.

[Filip]

Moved to feature requests and changed the title.

[Code-Jack]

I think the behavior is a bug.
I’m not asking for a feature (except in the Additional Context).

Sometimes the last weeks I’ve found some strangely distorted order in the Grid which I couldn’t explain.
Here now I could finally reproduce one possible cause for it.

Such an intransparent and strange behavior I call a bug.

[Filip]

If I remember correctly, this has worked like this since collections were introduced which probably means that it is intended. If it’s intended behavior, then it’s not a bug.
I’ll send it as a bug, but if I had to guess, it’ll probably immediately get moved from bugs to the product team.

[Angelo]

This report has been added to our issue tracker and received by the Development Team.

[AnyFriends]

This issue has been fixed by the Development Team and will be implemented in an upcoming release.