Question: Indented sub-tasks
I really like the flexibility of task relations, but I find myself wanting sub-tasks to be grouped and indented with the parent task.
I understand this can be complicated a lot since relations can be cross list and namespace, which is why I haven't attempted to implement this yet, but I'm hoping we can find an elegant solution.
This feature would be super useful - I would imagine it working like this: when the subtask is in the same list, it would show up indented below the parent task (like in Todoist). If it's from a different list, it would show up with a link as it does today.
And it would tie in perfectly with drag-and-drop (what I really miss in Vikunja) - you could drop any task below a different task, and it would become a subtask.
The hard part about this is a) how should this work with pagination? Should it still only show 50 tasks with some regrouped or 50 in total with some being reorganized to appear under their parent task? What should happen if a sub task would show up on a different page than its parent task?
Custom sorting per drag and drop would add extra complexity to the problem.
Yeah pagination definitely makes it more difficult. I personally would prefer the second option:
50 in total with some being reorganized to appear under their parent task
But that is in part because the curent ordering doesn't matter as much to me.
I agree that drag-and-drop would make this super convenient, but it definitely adds complexity
What if subtasks bypassed the limit of tasks per page and didn't count towards the total? That way you won't have subtasks split across multiple pages. If the concern is that too many subtasks will show at once, maybe we can cap their initial count at some value and add a "show more" button that will load more subtasks?
Drag and drop will definitely be harder, but I think it's a must have feature. I like dragging tasks around instead of them being sorted by some arbitrary value. Since the drag and drop feature already exists in Kanban, I think that a similar method could be adapted for list view.
maybe we can cap their initial count at some value and add a "show more" button that will load more subtasks?
I think that would make it even more complicated than it is already - I'd rather not implement that in a first version. If people complain, sure, but I doubt anyone has tasks with more than 20 subtasks or so.
I personally think subtasks should either be loaded underneath their master task, or at least allow for a view in the list where labels can be grouped together. This way if you want to say make a grocery list, you can specify the store you have to go to as the master, and all the items below it; then another store as a master and the other items below that.
For the second option, if you want, I can make a new issue for that since it is inherently different than the first.
Deleting a branch is permanent. It CANNOT be undone. Continue?