GothenburgBitFactory / GothenburgBitFactory/taskwarrior
[RFC] Nested tasks instead of projects
- Dominant language
- C++
- Stars
- 6.1k
- Forks
- 423
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 11
Description
Before I discovered taskwarrior I was thinking a lot about how I would like to structure my tasks. One thing I came up with was the fact that I want arbitrary hierarchies of tasks. When I discovered taskwarrior I was first unsure how fitting it is to that, but sort of accomodated to projects. But even though they might solve my problem in theory, it feels a little ugly: Whenever I find that a task should have multiple subtasks, I create a new project for it and add all the tasks to that project.
This is odd, because after reading https://github.com/GothenburgBitFactory/taskwarrior/issues/1807 I removed most projects and tried to make my tags more sensible. Yet I find myself drawn to create some hierarchy.
One of the main problems with projects is that this task I first created basically encompasses the whole project - often there are general steps that must be taken for the project. Then, when I see an appropriate subtask, I would create it as such, and when I'm done I continue working on the general task - that way, until a project is done, I always have a task that represents it, even if I don't currently have any smaller steps for it.
Oh, and don't suggest dependencies, it's already getting really messy over here...
Contributor guide
Assessment
This issue has not been assessed yet.