CLOSED: [2021-03-06 Sat 18:28] SCHEDULED: <2021-03-06 Sat>
:PROPERTIES:
:CREATED: [2021-03-06 Sat 17:22]
:ID: 2021-03-06-task-lifecycle
:END:
:LOGBOOK:
- State "DONE"       from "NEXT"       [2021-03-06 Sat 18:28]
:END:

This is an article from a series of blog postings. Please do read [[id:2019-09-25-using-orgmode][my
"Using Org Mode Features" (UOMF) series page]] for explanations on
articles of this series.

In this article, I give a brief overview on my current habit of using
Org mode [[https://orgmode.org/manual/TODO-Basics.html#TODO-Basics][todo keywords]], [[https://orgmode.org/manual/Deadlines-and-Scheduling.html][scheduled dates]] and [[id:2021-01-23-org-linker-edna][org-edna triggers]] to define the
life-cycle of an Org mode heading that is a task at least once.

-------------

#+CAPTION: My current Org mode task life-cycle.
#+ATTR_HTML: :align center :width 630 :linked-image-width original
[[tsfile:2021-03-06 my current life-cycl of an org mode task -- publicvoit.png][2021-03-06 my current life-cycl of an org mode task -- publicvoit.png]]

At the moment, I'm not using deadlines at all. My default todo keyword
is =NEXT=. I once used =TODO= as an unscheduled task and =NEXT= as a
scheduled one. However, I got rid of =TODO= altogether and use
=SOMEDAY= for this purpose which better reflects its character.

Most tasks are created with =NEXT= and a scheduled date and directly
go to =DONE= when solved.

I love to define tasks that are waiting for another task as a normal
heading without any todo keyword or scheduled date. When the depending
task is finished, this task then gets its keyword (usually =NEXT=) and
a scheduled date (usually today) [[id:2021-01-23-org-linker-edna][via org-edna automatically]]. This way,
I don't need recurring reviews in order to move [[id:2019-11-03-org-projects][my projects]] forward.