It would be amazing to have basic dependencies being reflected in the view.
Like, if a task is marked as parent of another task - or one task depends (blocks is is blocked by) another task: indicate it accordingly. It doesn’t have to be fancy, but just show the basic relations. E.g. via an arrow. Or grouping. Or whatever.
Asked differently: What are the relations about if not being shown / visualized in any view right now? Incentive to actually set such does not appear to make any immediate sense to me. What do relations do / affect at the very moment?
I can’t think of any proper design involving arrow/groupping on Kanban view.
I also strugle often to understand the bigger picture when particularly looking at one task out of whole hierarchy. And those tasks on same hierarchy are often named similarly given the shared general topic they cover so it’s very easy to get lost in the weeds.
What I suggest is having right-click button “Visualize Relations” that would open up a pop-up with read-only diagram showing particular task’s relations recursively.
I can’t think of any proper design involving arrow/groupping on Kanban view.
Maybe I’m just too naive here, but:
grouping: showing cards in a nested way, children inside parents inside grandparents?
dependencies: simple arrows, either with text-tags or color/pattern indicating it e.g. being a dependency - and direction indicating which depends on which.
At first, a big +1 from me! I also thought about such functionality.
A possible way could also to have just an icon on the task with a number and color, which then is the same on the related ones, for example.
Just to see, that they are related.
I do also see a possibility with Mermaid.js but only as an advanced option. It makes only sense when you really have a task with many subtask or of course related tasks. Which is probably not always the case.
For smaller kanban boards, it would be enough to have overview with one sight over the board via symbols as said for example.
Talking about arrows.
What if tasks are not on the same Kanban board?
What if related task is hidden down in bucket because it was not scrolled to yet?
Indicate that - e.g. arrow going into infinity / fading out. Or not supporting that.
What if related task is hidden down in bucket because it was not scrolled to yet?
I don’t know enough about “orders” of cards. Right now it feels arbitrary. The order of creation or how they got moved. Set priority or any other attribute doesn’t make a difference. So, e.g. sort by relation (if desired / by default / if “show relations” got activated) ?