Hi, it’s a design choice, the kanban event contain only the list where the item was added or moved.
Do you really need to update the others column items index ? Even if it create a void between index 0 and 2 for exemple it will still be ordered correctly, and if you move something inside this column the correct index will be applied and it will no longer have a “void”
If its important for you, you can instead put a workflow on the stack, you will have a workflow on add, on remove, and on move.
So when you move item 2 from category 2 to category 3
- it will trigger on add on cat 3, with the new list of cat 3
- It will trigger on remove on cat 2, with the new list of cat 2
And so you will be able to update the index of every items impacted by the change