How do you handle single steps for todos?

Questions & Help
2

I would like to share with you how I am tackling the problem so far…

Quick TODOs like “call someone back” are not the issue here. I enter them directly in the journal and work through them as quickly as possible.

But I treat larger tasks quite differently:
The main task (the subject of the task) is NOT marked as TODO, but with the tag #BACKLOG.task. The single steps that have to be done to complete the task are marked as TODOs and subtasks are only marked with a :footprints: (further steps to take). This way I avoid having too many TODOs on different levels.

I see all my main tasks on the page “BACKLOG.task” and if a main task is completed I rename it to “BACKLOG.done”.

An example would be:

[#A] #BACKLOG.task organise workshop for project XY.
 - 🔲 TODO set topics
     - 👣 → brainstorming
     - 👣 → agree on the content with the team
     - 👣 → define agenda
 - 🔲 TODO find a suitable date
     - 👣 → and so on ...

If I start one of the :footprints: (subtasks) I use the shortcut to transform them into a TODO.

I think a solution with an extra workflow status for subtask (TODO, DOING, WAITING, “subtask”) would be more elegant - but this is working for me quite well.

Are you doing something similar?

1 Like