Sort-by-function glitches out and becomes unusable (in grid view), when objects are reordered in Kanban view

What’s The Bug?

The sorting function doesn’t work (sorts objects in a completely random order) in grid view when objects are moved around in Kanban view in a collection/query.

When sorting my objects by property ‘status’ (a select property) they appeared to be in completely random order in both ‘ascending’ and ‘descending’ sort. Deleting and remaking the property fixed the issue, but as soon as I created a Kanban view which grouped by the new property, once I returned to the grid view, sort now reordered it into a random order and no longer worked.

How To Reproduce It

  1. Create a collection of objects with grid view
  2. Create a ‘select’ property and create multiple options, numbers make it more clear (this does not appear to happen with ‘multi-select’)
  3. Apply the property to the collection of objects and assign the values to each object
    3.5. Check the ‘sort by [your property]’ is working correctly
  4. Add Kanban View and group by [your property]
  5. Rearrange objects in Kanban view
    Once you return to grid view, the objects are out of order and the sorting function is broken.

Image or Video


The Expected Behavior

After using Kanban Vvew, it is expected that the objects will still be able to sort properly in grid view.

Device

Macbook Pro M4 Pro

OS

Sequoia 15.3.2

Anytype Version

0.47.6

Network Mode

AnySync

Technical Information

A8fbSyASTpz5CwSGq9XrCyJBxoeWv9GttqVkPbmejbfDy6SX

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

I’ve also been experiencing many more bugs brought on by Kanban view - it doesn’t feel as polished as the other views. Here is a few:

  • When filtering queries in Kanban view, certain projects do not show up in ‘linked projects’ list. A restart sometimes fixes this but not always.
  • I have multiple instances in which my tasks do not show up in Kanban view but do in grid view (these are in queries with filters on). I have ensured the sort-by is set to the correct property

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