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 5c6be117fe

Resolves https://community.vikunja.io/t/warning-when-moving-tasks-to-a-bucket-with-limit/3520
This commit is contained in:
kolaente 2025-03-19 16:06:03 +01:00
parent 617070f9f7
commit beb711d38c
No known key found for this signature in database
GPG Key ID: F40E70337AB24C9B
1 changed files with 1 additions and 0 deletions

View File

@ -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)
}