Details/Description for Tasks

[m4po5]

related to issues:

• Line break in a card? #25
• Sub-tasks should move with parent #18

Requirement Description

To work with TODOs/Tasks, I require them to be more detailed. I usually put useful information into the description, reaching from user-stories about tech-refs to links for further information.

That's because I use TODOs to plan my team's work, especially during startup.

• What do I need to do? ➡️ collect features, infrastructure-reqs, ets. into TODOs
• Within each ticket
  • What do I need to do specifically? ➡️ list criteria, point out hazards, expose dependencies within project
• With all that information ➡️ Maybe cut TODOs into separate tasks and subtasks, order by priority / dependency

Ideas

Perhaps allow for tasks to be written in their own file? The filename (minus .md extension) has to be the same as that of the task within the TODO.md. Since this is working against the filesystem, there's no need to worry about IDs.

Those tickets could move into a .todos subfolder that I wouldn't mind dragging along, where all my TODO-tickets reside in.

I never developed a VS Code extension, so I'm unaware of its limits. But if clicking on a ticket within the Task Board could open the description, or even preview some key features like you already introduced through types, dates and who's working on it, would really elevate this product.

Though that doesn't really solve the subtask issue, yet.

Subtasks

It's related because I think this is a philosophical question: Are subtasks handled exactly like independent tasks, or are they actually part of another task they should stick with?

Either way, if tasks get their own file each, the whole reference problem could be solved by the same means like my request for details. Within a ticket file is a ### Sub-Tasks subsection, which lists all the filenames of the subtasks.

Now, if you want to move subtasks with the parent, the Task Board could figure out such relations through the parent-ticket.

Should subtasks remain something independent, which I prefer slightly, you might still be able to add a visual component to the Task Board to highlight their relation? Perhaps subtasks get their own icon and a little button to navigate to the parent task, while parent tasks get a purely graphical list of their subtasks to visualize which of them are done or not.

Background

I use the MD format a lot for documentation and VS Code for quite a ton of development / maintenance tasks. It would be a HUGE benefit for me and my colleagues if you could make these features possible! 😄