Unable to have anything beyond done bucket in Kanban #2190

New Issue

xeruf · 2024-03-11T11:17:46Z

xeruf commented

2024-03-11 11:17:46 +00:00

Description

We have a Check/Review bucket which is marked as Done bucket, so that tasks that are checked off in list view are reviewed before they are stashed away for good in the bucket named "Done". But when moving those tasks over to the "Done" bucket, they are marked undone, because it is not recognized as a Done bucket by Vikunja. Not sure how to sensibly solve this though. I guess the Kanban rework making task states individual will solve it, but until then this is a major problem in our workflow.

Vikunja Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

### Description We have a Check/Review bucket which is marked as Done bucket, so that tasks that are checked off in list view are reviewed before they are stashed away for good in the bucket named "Done". But when moving those tasks over to the "Done" bucket, they are marked undone, because it is not recognized as a Done bucket by Vikunja. Not sure how to sensibly solve this though. I guess the Kanban rework making task states individual will solve it, but until then this is a major problem in our workflow. ### Vikunja Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_

xeruf added the

kind/bug

label 2024-03-11 11:17:46 +00:00

konrad commented

2024-03-11 11:20:19 +00:00

I would solve this with a label "needs review" or similar instead of using the "Done" bucket status for tasks which are not really done yet.

xeruf commented

2024-03-11 11:24:54 +00:00

But then if you are working on the task you need to go into the task details view and meddle with labels rather than just hitting the satisfying checkbox, and everybody needs to be taught that.
Actually at that point you may just stay in Kanban and move it manually rather than adding a label, but the whole point was to make it portable.
Maybe a temporary fairly easy fix could be to allow multiple done buckets and automatically move done tasks to the first or last one, if the data structure allows that?

But then if you are working on the task you need to go into the task details view and meddle with labels rather than just hitting the satisfying checkbox, and everybody needs to be taught that. Actually at that point you may just stay in Kanban and move it manually rather than adding a label, but the whole point was to make it portable. Maybe a temporary fairly easy fix could be to allow multiple done buckets and automatically move done tasks to the first or last one, if the data structure allows that?

konrad commented

2024-03-11 12:50:07 +00:00

Maybe a temporary fairly easy fix could be to allow multiple done buckets and automatically move done tasks to the first or last one, if the data structure allows that?

I wouldn't say this is an "easy" fix, I think we better solve that with the more flexible views.

To me, the problem you're having sounds like a process issue, not a software issue.

> Maybe a temporary fairly easy fix could be to allow multiple done buckets and automatically move done tasks to the first or last one, if the data structure allows that? I wouldn't say this is an "easy" fix, I think we better solve that with the more flexible views. To me, the problem you're having sounds like a process issue, not a software issue.

👍 2

renovate referenced this issue from a commit

2024-04-01 15:07:09 +00:00

chore(deps): update dependency netlify-cli to v10.13.0 (#2190)

dpschen commented

2024-07-16 21:06:41 +00:00

@xeruf:
Might be, that I misunderstand this, but why don't you use the bucket named 'Done' as the Vikunja done bucket?

@xeruf: Might be, that I misunderstand this, but why don't you use the bucket named 'Done' as the Vikunja done bucket?

Sign in to join this conversation.