[GH-ISSUE #1392] Kanban view does not save when a task is moved to another bucket #6381

Closed
opened 2026-04-20 16:58:22 -05:00 by GiteaMirror · 11 comments
Owner

Originally created by @ruanformigoni on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1392

Description

When tasks are moved from a bucket to another, only a couple are actually moved. If the page is refreshed, some will be back on the original bucket and some will be mixed in the target bucket.

Vikunja Version

v1.0.0-rc1

Browser and version

Firefox 141.0.3 (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @ruanformigoni on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1392 ### Description When tasks are moved from a bucket to another, only a couple are actually moved. If the page is refreshed, some will be back on the original bucket and some will be mixed in the target bucket. ### Vikunja Version v1.0.0-rc1 ### Browser and version Firefox 141.0.3 (64-bit) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Sep 2, 2025):

Are you using typesense?

<!-- gh-comment-id:3246672031 --> @kolaente commented on GitHub (Sep 2, 2025): Are you using typesense?
Author
Owner

@ruanformigoni commented on GitHub (Sep 2, 2025):

No, I tried to create another kanban to reproduce, but it worked fine. Maybe it has to do with the number of cards? Since the one I'm using has 80+.

<!-- gh-comment-id:3246688211 --> @ruanformigoni commented on GitHub (Sep 2, 2025): No, I tried to create another kanban to reproduce, but it worked fine. Maybe it has to do with the number of cards? Since the one I'm using has 80+.
Author
Owner

@kolaente commented on GitHub (Sep 2, 2025):

It shouldn't depend on the number of cards. Does it work with the latest unstable build?

<!-- gh-comment-id:3246707024 --> @kolaente commented on GitHub (Sep 2, 2025): It shouldn't depend on the number of cards. Does it work with the latest unstable build?
Author
Owner

@ruanformigoni commented on GitHub (Sep 2, 2025):

The problem seems related to the browser:

  • I pulled the latest unstable build to use on compose (on my server machine), and that did not fix it.
  • I cleared the cache of Firefox and restarted it (on my client machine), now it seems to be working fine.
<!-- gh-comment-id:3246734498 --> @ruanformigoni commented on GitHub (Sep 2, 2025): The problem seems related to the browser: - I pulled the latest unstable build to use on compose (on my server machine), and that did not fix it. - I cleared the cache of Firefox and restarted it (on my client machine), now it seems to be working fine.
Author
Owner

@kolaente commented on GitHub (Sep 2, 2025):

That's really odd, but glad you found a solution. I'll close this as resolved, please ping if you discover a way to reliably reproduce it.

<!-- gh-comment-id:3246740581 --> @kolaente commented on GitHub (Sep 2, 2025): That's really odd, but glad you found a solution. I'll close this as resolved, please ping if you discover a way to reliably reproduce it.
Author
Owner

@pleonex commented on GitHub (Nov 10, 2025):

I've been having the same issue for a while now, running 1.0-rc-2 with containers. It happens from time to time, from Firefox and Google Chrome and even from different devices.

Today I think I was able to reproduce it more consistently. It happens when a kanban bucket has more than ~20 tasks, so it requires fetching tasks from the second page of the bucket. In that case, moving a task from that non-first page of the bucket will fail.

When the issue happens I see only one POST operation to the endpoint api/v1/tasks/{TASK_ID}/position. But, it's missing the second POST operation that there is when it really succeeds /api/v1/projects/{ID}/views/{ID}/buckets/{ID}/tasks.
The task is not moved to the second bucket, but after a page refresh it shows near the top of initial bucket (I guess in its first query page).

<!-- gh-comment-id:3510506763 --> @pleonex commented on GitHub (Nov 10, 2025): I've been having the same issue for a while now, running 1.0-rc-2 with containers. It happens from time to time, from Firefox and Google Chrome and even from different devices. Today I think I was able to reproduce it more consistently. It happens when a kanban bucket has more than ~20 tasks, so it requires fetching tasks from the second page of the bucket. In that case, moving a task from that non-first page of the bucket will fail. When the issue happens I see only one POST operation to the endpoint `api/v1/tasks/{TASK_ID}/position`. But, it's missing the second POST operation that there is when it really succeeds `/api/v1/projects/{ID}/views/{ID}/buckets/{ID}/tasks`. The task is not moved to the second bucket, but after a page refresh it shows near the top of initial bucket (I guess in its first query page).
Author
Owner

@kolaente commented on GitHub (Nov 11, 2025):

@pleonex I've tried to reproduce it just now with the latest unstable build, are you able to reproduce it with that? The demo runs on unstable, please check there.

<!-- gh-comment-id:3515914088 --> @kolaente commented on GitHub (Nov 11, 2025): @pleonex I've tried to reproduce it just now with the latest unstable build, are you able to reproduce it with that? [The demo](https://try.vikunja.io) runs on unstable, please check there.
Author
Owner

@pleonex commented on GitHub (Nov 11, 2025):

I was able to reproduce it with the demo instance with the project Issue1392.
From the kanban view, if I try to move one of the tasks from the bottom of the column "To-Do" (like "Task 3") to the "Doing" column, it seems it has been moved, but after a refresh (F5), it appears back in "To-Do".

<!-- gh-comment-id:3516180532 --> @pleonex commented on GitHub (Nov 11, 2025): I was able to reproduce it with the demo instance with the [project Issue1392](https://try.vikunja.io/projects/83/576). From the kanban view, if I try to move one of the tasks from the bottom of the column "To-Do" (like "Task 3") to the "Doing" column, it seems it has been moved, but after a refresh (F5), it appears back in "To-Do".
Author
Owner

@kolaente commented on GitHub (Nov 15, 2025):

Should be fixed now in 411cfbef92, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

<!-- gh-comment-id:3536619388 --> @kolaente commented on GitHub (Nov 15, 2025): Should be fixed now in https://github.com/go-vikunja/vikunja/commit/411cfbef92d6662b226f41b4b2e3b9a84138ea46, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
Author
Owner

@ruanformigoni commented on GitHub (Nov 15, 2025):

Hi @kolaente, thank you! I pulled f8565a3e75ef and it seems fixed.

<!-- gh-comment-id:3536727926 --> @ruanformigoni commented on GitHub (Nov 15, 2025): Hi @kolaente, thank you! I pulled [f8565a3e75ef](https://hub.docker.com/layers/vikunja/vikunja/unstable/images/sha256-f8565a3e75ef4bae444cf37ade3b1323d0d24fbfd85be2caf0017a9a524bd819) and it seems fixed.
Author
Owner

@pleonex commented on GitHub (Nov 16, 2025):

I can also confirm that the issue seems to be fixed with the latest unstable build. Thanks a lot!

<!-- gh-comment-id:3539497283 --> @pleonex commented on GitHub (Nov 16, 2025): I can also confirm that the issue seems to be fixed with the latest unstable build. Thanks a lot!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6381