Done bucket behaviour #1796
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1796
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Few things I noticed about the "Done" bucket in KanBan mode:
Finally, a kind of unrelated item I found while verifying the above items:
There was another condition, but I couldn't remember it until now:
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.
Agreed, that sounds like a bug.
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.
Although edge-casey, I think that would make sense.
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.
If there is no history for the task, then I guess you could move it back to the default (first) bucket.
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...
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.)
If you'd only move them to the next bucket left then yeah, the detail view wouldn't make a difference.
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:
And Wekan integrates it with the comments, which seems a sensible approach for Vikunja:
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.
Agreed, there's an item in the backlog for this already.
One day, Vikunja will be integrated with Gitea for issue tracking, and this duplication won't be needed anymore ;)
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.
Adding these two links to stuff that we currently are working on / are on out roadmap regarding kanban:
See also vikunja/frontend#2338 and vikunja/frontend#2246
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.
And marking a bucket as Done should offer to move all done tasks to it
This should be relatively easy once we have bulk updates.