manage complex projects in taskwarrior using tasks tagged with epic
taskwarrior.epics is the work of Tom Elliott (email@example.com). Copyright (c) 2019 Tom Elliott. See LICENSE.txt file for complete license.
Run the script to learn more about how the "projects" attribute is being used in your taskwarrior database:
You'll get a result on stdout like:
Taskwarrior Project Report ========================== active projects: 82 tasks without projects: 112 projects with a single epic: 11 projects without epics: 69 abbreviations accessibility ... projects with too many epics: 2 preservation (2) taskwarrior epics (2)
- an on-going, discrete domain or area or initiative of work of life, e.g., "health" or "pleiades"
- a major, coherent activity within a particular programme domain that requires multiple tasks to complete
- a task/action that embodies the end/completion state of a project. One epic per project. Once the epic is done, the project is done.
- a task as defined by task warrior (action in GTD): a discrete, atomic piece of work
get list of projects (
- list of problems like no epic, too many epics, etc.
- description (where to store this? maybe
- epic task
- first action for the epic
- associated project folders, messages, online links
- due dates
get taskwarrior orphans/incompletes; i.e., projects without:
tasks(projects are defined by the project attribute on tasks, so they cannot exist without at least one task)
- programme association (NB:
how to manage/make use of a list of active programmes a list of active projects, etc.