I’m using the docker hosted version of Vikunja, deploying the latest after updates.
Currently v0.24.2, I started on 0.24.0.
I’ve noticed that on many of my projects (boards?), the cards are out of order in a bucket. They do not seem to be based on creation date or ID number. At first I just thought this was how things are, but I have realized that this is probably a bug.
This is the default ordering of this bucket (I have not moved cards in this bucket):
The most annoying part has been when creating a new card with the “Add another task” button, it would usually show the card at the bottom, and then after a page refresh, the card would be in another spot in the bucket. Sometimes the card would move to a seemingly random point in the list right after creating it.
I would expect that creating a new task (card) should add it to the bottom of that bucket, and not move it until I move it.
I’m unable to reproduce this on a new project or list, since I’m unsure when it really started. Very occasionally I have seen cards duplicated visually (but go away after a refresh) - might be related to the other bugs I saw about projects and duplication.
I started my instance by creating lots of Projects first to organize things and making and moving and deleting many buckets. So I’m guessing it was something in that process.
TEMP FIX:
I think I’m able to fix things for the moment by deleting my current Kanban view and creating it again. I’ve noticed a new kanban view orders the cards by their #ID which is the behaviour I would expect.
What is the expected ordering behaviour for new tasks added directly to the bucket, as well as from cards moved from another Project?
This is now fixed in 429c7ca2c1, please check with the next unstable build (should be ready for deployment in ~45min, also on try).
I’ve decided to move new tasks always to the top, since that was planned anyway and makes it a lot easier to do something with the task after creating it.
I used Kanbans extensively last year and they were very well behaved. Just started using them again and the cards have a mind of their own - its near unusable.
Im on the lastest docker image, issue persists in Safari and Firefox
@kolaente I’ll also add onto this that I have had ordering issues on Kanban boards of late in Vikunja as well. Has worked perfectly fine for years before this.
I’m guessing this is tied into the above ordering issue reports, but within any given Kanban bucket I used to be able to manually order tasks. Now it works fine for the first task I move and none after that until I refresh the browser. I can replicate this on try as well. As an example:
I create 3 tasks in the backlog bucket: task1, task2, task3.
I then move task2 and task3 before task1.
I refresh the browser.
Task2 will move before task1, but task3 will not have moved.
Note that this does not seem to impact tasks moving between kanban buckets.
Thanks for looking into this @kolaente. I’m unable to test the latest unstable since I’m using the docker, but I did look at it on try.vikunja.
I’m able to replicate what @mcsgroi said, so things don’t seem to be working properly just yet.
I understand the reasoning for creating the new card at the top of the list, however the UX on that is a bit disorientating, because to add a new card with details, you must now first move the mouse down to the bottom of the screen and click “Add another task”, followed by moving it up to the top of the bucket and clicking the task you just created.
It’s something I could get used to but seems unintuitive. Perhaps “+ Add Another Task” should be at the top if it stays like this (which is different to how trello and other agile boards behave).
Still - this update is much better than losing the task in the middle of the list!
The reasoning here is this works fine as long as you don’t have that many tasks. As soon as you need to scroll to see the new task, there’s a moment of “where did that task go which I just created”. Adding new tasks to the top was already planned for a while, in fixing the bug here I just noticed how it made sense to do this now.
I am having the same issue on the self hosted (version: v0.24.3), but I believe I have a work-around. After I add/remove cards from a bucket and/or reordering them, I double-click on one of the cards and open the details, then close it again. This seems to make the changes stick.
