Task priorities

Todowl has four priority levels and one colour language for all of them. Priority is set in the task detail panel or from the task’s context menu.

The four levels

Level	Colour
None	Grey
Low	Blue
Medium	Orange
High	Red

None is the default, and it is not a failure state. Most tasks should stay there.

Where the colour shows up

The same colour is used for a task everywhere it appears:

• the checkbox outline
• the stripe and tint on a kanban card
• the flag glyph in the list
• the group header when the list is grouped by priority

They all read from one source in the code, so they can never drift apart. That consistency is the point: you learn one colour scale, and it means the same thing on every screen.

Setting priority

Open a task and use the priority row in the detail panel, or right click the task and pick from the menu. Both change the same field.

Using it without inflation

Priority stops being information the moment everything is high. Two rules keep it useful:

• High is for today. If a task is high priority but scheduled for next month, it is not high priority, it is just important, and the date already says that.
• Cap the count. Two or three high priority tasks at once is a plan. Nine is a mood.

Low priority is the more underused half of the scale. It is a good marker for things you genuinely want to do but would happily drop, and colouring them blue makes them easy to skip when the day gets short.

Priority and dates do different jobs

A date says when. Priority says how much it matters if it slips. They answer different questions, and a task that has both is much easier to triage than one that has either alone.