github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Unable to have anything beyond done bucket in Kanban #464

New Issue
Open
opened 2025-11-01 20:56:33 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 20:56:33 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by xeruf on 2024-03-11T11:17:46.000Z

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

Original issue on Gitea

@kolaente commented on 2024-03-11T11:20:19.000Z:

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 on 2024-03-11T11:24:54.000Z:

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?

@kolaente commented on 2024-03-11T12:50:07.000Z:

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.

dpschen commented on 2024-07-16T21:06:41.000Z:

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

xeruf commented on 2024-12-10T20:49:02.000Z:

Because when you check off a task in the list view, I want it to go to the review bucket

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by xeruf on 2024-03-11T11:17:46.000Z_ ### 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_ [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/2190) --- _**@kolaente** commented on 2024-03-11T11:20:19.000Z_: 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 on 2024-03-11T11:24:54.000Z_: 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? --- _**@kolaente** commented on 2024-03-11T12:50:07.000Z_: > 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. --- _**dpschen** commented on 2024-07-16T21:06:41.000Z_: @xeruf: Might be, that I misunderstand this, but why don't you use the bucket named 'Done' as the Vikunja done bucket? --- _**xeruf** commented on 2024-12-10T20:49:02.000Z_: Because when you check off a task in the list view, I want it to go to the review bucket
GiteaMirror added the kind/bug label 2025-11-01 20:56:33 -05:00
GiteaMirror commented 2025-11-01 20:56:34 -05:00
Author
Owner
Copy Link

@xeruf commented on GitHub (Sep 8, 2025):

This is coming up again and again - essentially we need stages of done-ness that the checkbox cycles through

I think moving across buckets when clicking the checkbox would be ideal, maybe with different icons inside the checkbox for indication, or automatic labels matching the buckets which complements https://community.vikunja.io/t/map-kanban-columns-to-filters/767/2 / https://github.com/go-vikunja/vikunja/issues/1390 / https://community.vikunja.io/t/allow-to-associate-kanban-buckets-to-labels/3399

@xeruf commented on GitHub (Sep 8, 2025): This is coming up again and again - essentially we need stages of done-ness that the checkbox cycles through I think moving across buckets when clicking the checkbox would be ideal, maybe with different icons inside the checkbox for indication, or automatic labels matching the buckets which complements https://community.vikunja.io/t/map-kanban-columns-to-filters/767/2 / https://github.com/go-vikunja/vikunja/issues/1390 / https://community.vikunja.io/t/allow-to-associate-kanban-buckets-to-labels/3399
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label kind/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#464
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?