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