Docs / Sorting, editing, and archiving

Sorting, editing, and archiving

The day-to-day mechanics of the task list — what each control does and why.

Sorting

Click Priority, Task, System, Deadline, Age, or Status to sort; click again to reverse. Priority is the default. Tasks with no deadline always sort last in both directions — an absent deadline isn't "very early" or "very late," it's just missing. Status sorts by urgency (Blocked → In progress → To do → Done), not alphabetically.

Editing a synced task

The source system is written first. If that call fails, the local row is left untouched, so Z3NTRA and the source never silently disagree. On success, the local row is updated with whatever the source echoed back — which is why the status column can show both the canonical status and the source's own wording (e.g. "Done" / "Complete").

Manual tasks

Created with + New task, shown with the system Manual. They live only in Z3NTRA and are the only tasks that can be deleted from here — deleting a synced task locally would just bring it back on the next sync, so that's blocked with an explanation instead.

Pinning and snoozing

Pin forces something to the top regardless of score. Snooze pushes it out of the list until a date you choose — which is recorded as a deferral, and comes back to you as an observation under Working patterns if you keep doing it to the same task.

Statuses

Four canonical values — To do, In progress, Blocked, Done — with each provider's own vocabulary mapped in and out. The mapping is keyword-based rather than a fixed table, so unusual states ("Ready for QA," "Awaiting client") still land somewhere sensible, and an explicit override always wins.

Archiving

A task that stops coming back from a sync is marked archived, not deleted — it may just have fallen out of the query rather than actually being gone. Tick Show archived to see them.