Moving tasks to done bucket does not mark them done anymore #2518

New Issue

ce72 · 2024-07-04T15:13:37Z

ce72 commented

2024-07-04 15:13:37 +00:00

Description

When moving (drag&drop) a task to a bucket which is marked as "Done bucket" the task remains undone.
This seems to be a regression to 0.23.0 where moving tasks to done bucket automatically marked them as done (which was the main purpose labeling the bucket as "Done bucket", or?)

Vikunja Version

0.24.0

Browser and version

chrome

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

### Description When moving (drag&drop) a task to a bucket which is marked as "Done bucket" the task remains undone. This seems to be a regression to 0.23.0 where moving tasks to done bucket automatically marked them as done (which was the main purpose labeling the bucket as "Done bucket", or?) ### Vikunja Version 0.24.0 ### Browser and version chrome ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_

ce72 added the

kind/bug

label 2024-07-04 15:13:37 +00:00

ce72 commented

2024-07-04 15:19:11 +00:00

to be more precisely: you have to reload the page to see it marked.

konrad commented

2024-07-05 11:55:48 +00:00

There's a video and a little more information related to this here: https://github.com/go-vikunja/vikunja/issues/280

koalp commented

2024-07-05 16:54:36 +00:00

There are other issues that I found with the kanban views :

when a task is created in a bucket, after refreshing it is not in the bucket it has been created but in the default bucket.
when you move a tasks from a bucket with a limit that is reached to another bucket, the counter is not updated until refresh, and you cannot add a task to this bucket (because the frontend still think the bucket is full I guess)

I think that they are linked because you also have to refresh to update the view.

There are other issues that I found with the kanban views : - when a task is created in a bucket, after refreshing it is not in the bucket it has been created but in the default bucket. - when you move a tasks from a bucket with a limit that is reached to another bucket, the counter is not updated until refresh, and you cannot add a task to this bucket (because the frontend still think the bucket is full I guess) I think that they are linked because you also have to refresh to update the view.

konrad commented

2024-07-07 15:06:48 +00:00

@koalp They don't sound related to this, but are probably related to each other. Can you open a new issue?

koalp referenced this issue

2024-07-09 20:09:43 +00:00

Task created in a bucket goes to the default bucket #2543

koalp referenced this issue

2024-07-09 20:24:31 +00:00

Kanban: the task counter isn't refreshed correctly #2544

koalp commented

2024-07-09 20:25:20 +00:00

I opened two other issues, one for each bug I mentioned.

👍 1

konrad referenced this issue from a commit

2024-07-11 11:17:49 +00:00

fix(kanban): update task done status after moving it into done bucket

konrad closed this issue

2024-07-11 11:17:50 +00:00

konrad commented

2024-07-11 11:19:31 +00:00

The original issue here is now resolved in ec0c05fd47. Please check with the next unstable build if it's gone.

The original issue here is now resolved in https://kolaente.dev/vikunja/vikunja/commit/ec0c05fd47aac9963bc5581f194f2e36408ceb3c. Please check with the next unstable build if it's gone.

🎉 1 ✅ 2

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#2518