Consider this workflow:
It can’t be dragged between buckets unless you manually find it in the kanban view. With a crowded list, this can be difficult or impossible.
Suggest adding a drop down list with all the kanban buckets in the list to choose from which would allow the user to change the bucket the task is in from the task view.
I would just use the search bar from the filter popup on the Kanban board to achieve what you’re trying, but I get why it would make sense to be able to change the board from the task detail view.
Cross-referencing this old issue: #537 - [Feature Request] Be able to change KanBan buckets for a task from within the task. - frontend - Gitea
Ha! I totally forgot I had already added that. I searched on these community forums for something similar, but I didn’t check the gitea instance.
No worries, been there as well.
I’ve just moved the item up the backlog.
I want to support the request of @SteveDinn .
I switchted from Kanboard to Vikunja, and the only thing that I’m missing is the movement between kanban buckets.
Thanks.
+1 for this issue 
Is it possible to get this feature?
It is often really helpful when you are in a task to be able to move it directly.
At the moment I think this is only possible via drag and drop. That can be very difficult with lots of buckets.
Moving within the task would make it much easier.
Thank you
It’s still in the backlog. This has actually gotten more complicated because a task can now be in multiple buckets at the same time (because there can be multiple views per project). Not sure how we can do this in a good way.
But the buckets are the state in which a task is.
And a task can only ever be in one particular state. I really do not understand the multiple views argument.
Kind regards,
Patrick
@pmh A task can be in multiple kanban views, which each might have different columns. That means we would need to show all of these bucket options in the task detail view.
I got from the discussion in this thread that this is technically the case in Vikunja. I question if this is a valid model of tasks in a project.
In my experience there is a project with exactly one scrum or kanban board so all people collaborating have the same view. Similarly there is an agreed upon number of states that are mapped to scrum or kanban columns/buckets.
And what Vikunja calls buckets are essentially states of a task, IMHO.
What would be a use case of multiple kanban views?
I do not argue that “nobody ever needs this”, but if this is the single feature that makes another feature which is important to me more difficult to implement, I would like to argue for labels or a different way to edit the kanban bucket right in the “view/edit task” view.
See: Allow to associate kanban buckets to labels - #8 by pmh
Kind regards,
Patrick
Either way, we need to think about this when implementing this. The way the view model works, it’s not as straight forward to add this like other task properties. It’s not impossible, just a little complicated.
You can already create a kanban view where the buckets depend only on the labels, via a filter bucket kanban view.
I will definitely try this. Does that imply that when I move a task from one bucket to the next the label will change accordingly?
You see, you have the “board” view and you move tasks around. Great. And then you have the “task edit” view and you should have access to all properties of the task including its current bucket.
Kind regards,
Patrick
Unfortunately, not really, since the filter view is read-only. You won’t be able to move a task from one bucket into another in that view.