From beb711d38c9cfb6ceadee5ce60dfa12d2b856bac Mon Sep 17 00:00:00 2001 From: kolaente Date: Wed, 19 Mar 2025 16:06:03 +0100 Subject: [PATCH] fix(kanban): set new bucket id on task after moving it This fixes a bug where a bucket update in the api was not triggered because the task still had the old bucket id saved. This led to inconsistencies between what was visible in the UI and what was actually stored. Probably introduced in 5c6be117feb1fc28b0f5b5f2d343067562d71b88 Resolves https://community.vikunja.io/t/warning-when-moving-tasks-to-a-bucket-with-limit/3520 --- frontend/src/components/project/views/ProjectKanban.vue | 1 + 1 file changed, 1 insertion(+) diff --git a/frontend/src/components/project/views/ProjectKanban.vue b/frontend/src/components/project/views/ProjectKanban.vue index 75d8d1fd3..252aa3175 100644 --- a/frontend/src/components/project/views/ProjectKanban.vue +++ b/frontend/src/components/project/views/ProjectKanban.vue @@ -529,6 +529,7 @@ async function updateTaskPosition(e) { projectId: project.value.id, })) Object.assign(newTask, updatedTaskBucket.task) + newTask.bucketId = updatedTaskBucket.bucketId if (updatedTaskBucket.bucketId !== newTask.bucketId) { kanbanStore.moveTaskToBucket(newTask, updatedTaskBucket.bucketId) }