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

[GH-ISSUE #483] Done bucket behaviour #6176

New Issue
Open
opened 2026-04-20 16:47:09 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 16:47:09 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/483

Original issue by SteveDinn on 2021-06-09T22:39:51.000Z

Few things I noticed about the "Done" bucket in KanBan mode:

  • Dragging an item out of the "Done" bucket should un-set its "doneness".
  • You shouldn't be able to add a new task directly to the "Done" bucket. What would be the point?
  • When intially marking a bucket as the "Done" bucket, it should mark all the tasks currently in it as done. A warning dialog might be prudent here.

Finally, a kind of unrelated item I found while verifying the above items:

  • Setting an item to 100% complete should make it "Done".

Original issue on Gitea

SteveDinn commented on 2021-06-12T13:22:00.000Z:

There was another condition, but I couldn't remember it until now:

  • Marking an item as "not done" should move it out of the "Done" bucket -- Perhaps back to the default bucket.
    Is history kept for these tasks? Perhaps it could be moved to the bucket it was in before it was moved to the "Done" bucket.

@kolaente commented on 2021-06-13T15:34:36.000Z:

Dragging an item out of the "Done" bucket should un-set its "doneness".

Agreed, that sounds like a bug.

You shouldn't be able to add a new task directly to the "Done" bucket. What would be the point?

TBH, I did not consider that yet. Maybe to keep track of tasks you already did but forgot to add to the list before starting them? I don't know if that'd make sense.

Setting an item to 100% complete should make it "Done".

Although edge-casey, I think that would make sense.

Is history kept for these tasks? Perhaps it could be moved to the bucket it was in before it was moved to the "Done" bucket.

The history is not kept, so that wouldn't work. It could be something to think of if the history is persisted at some point in the future though.

SteveDinn commented on 2021-06-13T16:04:12.000Z:

If there is no history for the task, then I guess you could move it back to the default (first) bucket.

adrinux commented on 2021-08-12T11:17:40.000Z:

In kanban is there not a movement from left to right through the buckets with done being rightmost? (At least for ltr languages.)

Placing it in the next bucket left would make more sense to me than the first bucket.

Maybe that just means moving it out of 'Done' should be left to the user...

@kolaente commented on 2021-08-12T18:17:12.000Z:

Maybe that just means moving it out of 'Done' should be left to the user...

I'd agree, but then what should happen when the user "undoes" the task for example from the task detail view?

adrinux commented on 2021-08-18T12:12:51.000Z:

Maybe that just means moving it out of 'Done' should be left to the user...

I'd agree, but then what should happen when the user "undoes" the task for example from the task detail view?

Not entirely clear to me why using the detail view would make a difference. (I still think it would make most sense to move them to the next bucket left.)

@kolaente commented on 2021-08-18T15:09:23.000Z:

If you'd only move them to the next bucket left then yeah, the detail view wouldn't make a difference.

xeruf commented on 2022-07-09T01:28:19.000Z:

Actually, we switched to moving tasks right-to-left ;)
See https://notes.jorre.dev/notes/20200929113755-backwards_kanban.html

Anyways, I agree with all these issues, and I think keeping a history with an activity log when the task was moved or modified by whom would be great, even the otherwise quite lacking Nextcloud Deck has it:
image

And Wekan integrates it with the comments, which seems a sensible approach for Vikunja:
image

I think the ability to add tasks to the done bucket does no harm - for us the "Done" bucket is actually called "Check" and reviewed by the team regularly, so adding tasks there retroactivly makes sense - but yes, they should be checked off automatically.

@kolaente commented on 2022-07-11T10:45:39.000Z:

Anyways, I agree with all these issues, and I think keeping a history with an activity log when the task was moved or modified by whom would be great, even the otherwise quite lacking Nextcloud Deck has it:

Agreed, there's an item in the backlog for this already.

xeruf commented on 2022-07-11T13:40:19.000Z:

One day, Vikunja will be integrated with Gitea for issue tracking, and this duplication won't be needed anymore ;)

dpschen commented on 2022-09-30T11:27:21.000Z:

You shouldn't be able to add a new task directly to the "Done" bucket. What would be the point?

Just read this thread again and I disagre with this point.
Reason being: Sometimes you want to add a task later that you did already for the sake of documenting that you did it. This one extra button also doesn't really hurt. I also wouldn't add an option to make this user definable here because if we do that we'll end up having options for everything.

dpschen commented on 2022-09-30T11:37:27.000Z:

Adding these two links to stuff that we currently are working on / are on out roadmap regarding kanban:

  • We plan to move away from the current sortable.js wrapper that we use for the kanban functionality: https://my.vikunja.cloud/tasks/15846. Sortable.js itself is fine, just the vue plugin is currently not maintained. We already use a fork, but that basically just fixes a few things that were broken. The core of the plugin is written like it's for vue 2 (while we are now use vue 3) and I'm not aware of any plans to change that. We are still not sure which way we will go here but listed some alternatives in the task.
  • https://kolaente.dev/vikunja/frontend/pulls/1571: here we split the components of the kanban in order to reduce complexity. This should help us improve the reliabiltiy and functionality in the future and makes sense. Before we can go back to this we should finish the typescript migration and pinia integration.

xeruf commented on 2022-10-01T10:02:42.000Z:

See also https://kolaente.dev/vikunja/frontend/issues/2338 and https://kolaente.dev/vikunja/frontend/issues/2246

WofWca commented on 2023-03-23T15:54:37.000Z:

Dragging an item out of the "Done" bucket should un-set its "doneness"

I opened an MR for this: #3291

It makes sense, but could actually be breaking as some people might have an "archived" bucket or something. I guess adding a setting for this could work if required.

xeruf commented on 2023-08-31T14:27:55.000Z:

When intially marking a bucket as the "Done" bucket, it should mark all the tasks currently in it as done. A warning dialog might be prudent here.

And marking a bucket as Done should offer to move all done tasks to it

@kolaente commented on 2023-08-31T15:14:05.000Z:

This should be relatively easy once we have bulk updates.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/483 _Original issue by SteveDinn on 2021-06-09T22:39:51.000Z_ Few things I noticed about the "Done" bucket in KanBan mode: * Dragging an item out of the "Done" bucket should un-set its "doneness". * You shouldn't be able to add a new task directly to the "Done" bucket. What would be the point? * When intially marking a bucket as the "Done" bucket, it should mark all the tasks currently in it as done. A warning dialog might be prudent here. Finally, a kind of unrelated item I found while verifying the above items: * Setting an item to 100% complete should make it "Done". [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1796) --- _**SteveDinn** commented on 2021-06-12T13:22:00.000Z_: There was another condition, but I couldn't remember it until now: * Marking an item as "not done" should move it out of the "Done" bucket -- Perhaps back to the default bucket. Is history kept for these tasks? Perhaps it could be moved to the bucket it was in before it was moved to the "Done" bucket. --- _**@kolaente** commented on 2021-06-13T15:34:36.000Z_: > Dragging an item out of the "Done" bucket should un-set its "doneness". Agreed, that sounds like a bug. > You shouldn't be able to add a new task directly to the "Done" bucket. What would be the point? TBH, I did not consider that yet. Maybe to keep track of tasks you already did but forgot to add to the list before starting them? I don't know if that'd make sense. > Setting an item to 100% complete should make it "Done". Although edge-casey, I think that would make sense. > Is history kept for these tasks? Perhaps it could be moved to the bucket it was in before it was moved to the "Done" bucket. The history is not kept, so that wouldn't work. It could be something to think of if the history is persisted at some point in the future though. --- _**SteveDinn** commented on 2021-06-13T16:04:12.000Z_: If there is no history for the task, then I guess you could move it back to the default (first) bucket. --- _**adrinux** commented on 2021-08-12T11:17:40.000Z_: In kanban is there not a movement from left to right through the buckets with done being rightmost? (At least for ltr languages.) Placing it in the next bucket left would make more sense to me than the first bucket. Maybe that just means moving it out of 'Done' should be left to the user... --- _**@kolaente** commented on 2021-08-12T18:17:12.000Z_: > Maybe that just means moving it out of 'Done' should be left to the user... I'd agree, but then what should happen when the user "undoes" the task for example from the task detail view? --- _**adrinux** commented on 2021-08-18T12:12:51.000Z_: > > Maybe that just means moving it out of 'Done' should be left to the user... > > I'd agree, but then what should happen when the user "undoes" the task for example from the task detail view? Not entirely clear to me why using the detail view would make a difference. (I still think it would make most sense to move them to the next bucket left.) --- _**@kolaente** commented on 2021-08-18T15:09:23.000Z_: If you'd only move them to the next bucket left then yeah, the detail view wouldn't make a difference. --- _**xeruf** commented on 2022-07-09T01:28:19.000Z_: Actually, we switched to moving tasks right-to-left ;) See https://notes.jorre.dev/notes/20200929113755-backwards_kanban.html Anyways, I agree with all these issues, and I think keeping a history with an activity log when the task was moved or modified by whom would be great, even the otherwise quite lacking Nextcloud Deck has it: ![image](/attachments/ecdbc54b-52c9-4776-ac36-bb65b2d8a756) And Wekan integrates it with the comments, which seems a sensible approach for Vikunja: ![image](/attachments/2ba51c75-3493-4bc9-b273-66095297f956) I think the ability to add tasks to the done bucket does no harm - for us the "Done" bucket is actually called "Check" and reviewed by the team regularly, so adding tasks there retroactivly makes sense - but yes, they should be checked off automatically. --- _**@kolaente** commented on 2022-07-11T10:45:39.000Z_: > Anyways, I agree with all these issues, and I think keeping a history with an activity log when the task was moved or modified by whom would be great, even the otherwise quite lacking Nextcloud Deck has it: Agreed, there's an item in the backlog for this already. --- _**xeruf** commented on 2022-07-11T13:40:19.000Z_: One day, Vikunja will be integrated with Gitea for issue tracking, and this duplication won't be needed anymore ;) --- _**dpschen** commented on 2022-09-30T11:27:21.000Z_: > You shouldn't be able to add a new task directly to the "Done" bucket. What would be the point? Just read this thread again and I disagre with this point. Reason being: Sometimes you want to add a task later that you did already for the sake of documenting that you did it. This one extra button also doesn't really hurt. I also wouldn't add an option to make this user definable here because if we do that we'll end up having options for everything. --- _**dpschen** commented on 2022-09-30T11:37:27.000Z_: Adding these two links to stuff that we currently are working on / are on out roadmap regarding kanban: - We plan to move away from the current sortable.js wrapper that we use for the kanban functionality: https://my.vikunja.cloud/tasks/15846. Sortable.js itself is fine, just the vue plugin is currently not maintained. We already use a fork, but that basically just fixes a few things that were broken. The core of the plugin is written like it's for vue 2 (while we are now use vue 3) and I'm not aware of any plans to change that. We are still not sure which way we will go here but listed some alternatives in the task. - https://kolaente.dev/vikunja/frontend/pulls/1571: here we split the components of the kanban in order to reduce complexity. This should help us improve the reliabiltiy and functionality in the future and makes sense. Before we can go back to this we should finish the typescript migration and pinia integration. --- _**xeruf** commented on 2022-10-01T10:02:42.000Z_: See also https://kolaente.dev/vikunja/frontend/issues/2338 and https://kolaente.dev/vikunja/frontend/issues/2246 --- _**WofWca** commented on 2023-03-23T15:54:37.000Z_: > Dragging an item out of the "Done" bucket should un-set its "doneness" I opened an MR for this: #3291 It makes sense, but could actually be breaking as some people might have an "archived" bucket or something. I guess adding a setting for this could work if required. --- _**xeruf** commented on 2023-08-31T14:27:55.000Z_: > When intially marking a bucket as the "Done" bucket, it should mark all the tasks currently in it as done. A warning dialog might be prudent here. And marking a bucket as Done should offer to move all done tasks to it --- _**@kolaente** commented on 2023-08-31T15:14:05.000Z_: This should be relatively easy once we have bulk updates.
GiteaMirror added the area/kanban label 2026-04-20 16:47:09 -05:00
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 area/kanban
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#6176
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?