Nuanced priority usage
If you are just starting out with Lunatask, feel free to skip this article.
Higher priority does not always mean the task should always be done before other tasks with lower priority.
Imagine a case when you have only one Started
task in the list. Now, a new more important task is added to Next
. Assigning the highest priority will now make the task in Next
more urgent than the task in Started
, hence it appears on top of the list in Now / Later workflow, and it will be highlighted as the next task to work on.
Assigning the priority of High
to the task in Next
won't have the same effect. You can use the priority of High
to sort your next tasks to work on after you finish the work you already started.
Similarly, this can be applied to Low
and Lowest
priorities. Assigning a lower priority to a task in Started
means putting it on hold for a while.
See the table below for the exact order of rules in workflows based on task status (higher in the list means more urgent).
Status | Priority |
---|---|
Due | Highest |
Started | Highest |
Next | Highest |
Due | High |
Due | Normal |
Started | High |
Started | Normal |
Next | High |
Next | Normal |
Due | Low |
Started | Low |
Next | Low |
Due | Lowest |
Started | Lowest |
Next | Lowest |
Waiting | Highest |
Waiting | High |
Waiting | Normal |
Later | Highest |
Later | High |
Later | Normal |
Waiting | Low |
Waiting | Lowest |
Later | Low |
Later | Lowest |
And here for Must/Should/Want method workflow:
Motivation | Priority |
---|---|
Due | Highest |
Must | Highest |
Should | Highest |
Want | Highest |
Due | High |
Due | Normal |
Must | High |
Must | Normal |
Should | High |
Should | Normal |
Want | High |
Want | Normal |
Due | Low |
Must | Low |
Should | Low |
Want | Low |
Due | Lowest |
Must | Lowest |
Should | Lowest |
Want | Lowest |
Unknown | Highest |
Unknown | High |
Unknown | Normal |
Unknown | Low |
Unknown | Lowest |