Question: Indented sub-tasks #363

Open
opened 1 month ago by azymondrian · 8 comments

I really like the flexibility of task relations, but I find myself wanting sub-tasks to be grouped and indented with the parent task.

My general use case of creating a task with subtasks usually ends up looking like the attached screenshot, which feels a bit awkward to me.

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.

I really like the flexibility of task relations, but I find myself wanting sub-tasks to be grouped and indented with the parent task. My general use case of creating a task with subtasks usually ends up looking like the attached screenshot, which feels a bit awkward to me. ![](https://kolaente.dev/attachments/117fb894-cd42-44bb-975d-e57bc65d5aec) 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.
Poster
Owner

You mean you want to see all sub tasks a task has in the list view?

You mean you want to see all sub tasks a task has in the list view?
Poster

This is a very rough mockup of how I typically picture a task with subtasks. I don't know how this would work with sub-tasks or a parent-task in a different list/namespace though.

This is a very rough mockup of how I typically picture a task with subtasks. I don't know how this would work with sub-tasks or a parent-task in a different list/namespace though. ![](https://kolaente.dev/attachments/57768601-8fe9-4dec-a2b9-a82089a3c2b8)
Poster

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.

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.
Poster
Owner

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.

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.
Poster

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

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
Poster

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.

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.
Poster
Owner

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.

> 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.
Poster
Owner

For drag n drop please see the discussion in #115

For drag n drop please see the discussion in https://kolaente.dev/vikunja/frontend/issues/115
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.