I have yet to understand where this kanban board stuff makes sense. Apparently, the Agile philosophy [0] introduced this to the software development world. Most implementations (Gitlab, Wekan) seem to miss central features (limits, cycle time stats).
I guess those boards serve as a issue tracker extension for short term development? How does that improve the process? Why do you need that on top of an issue tracker? Replacing the issue tracker is probably not idea?
I guess those boards serve as a issue tracker extension for short term development? How does that improve the process? Why do you need that on top of an issue tracker? Replacing the issue tracker is probably not idea?
[0] https://www.atlassian.com/agile/kanban