Vigile
SearchContents

How it works

Next and waiting

Nobody marks a task as ready or as blocked. Whether it can start is worked out from the plan each time someone asks.

Next and waiting, worked out from statuses and links Four tasks in a chain of dependencies. Stored: WEB-002 is done; WEB-003, WEB-004 and WEB-013 are open. Worked out on every read: WEB-002 is finished, WEB-003 is next, WEB-004 waits for WEB-003, and WEB-013 waits for WEB-004. STORED: STATUSES AND LINKS WEB-002 Cart page status: done WEB-003 Payment form status: open WEB-004 Confirmation email status: open WEB-013 Launch status: open WORKED OUT ON EVERY READ finished next: can start waiting for WEB-003 waiting for WEB-004 Finish WEB-003, and WEB-004 is next for whoever asks after that. No flag was updated, because there is none: only the status of WEB-003 changed.
The cart page is done, so the payment form is next. The confirmation email waits for the payment form, and the launch waits for the confirmation email. The statuses and the links are what is stored; next and waiting are worked out from them each time they are read.

Two words, worked out

  • Next: The task is open, is not deleted, has an active path through its projects and groups, and has no unfinished dependency. It can start now.
  • Waiting: The task is not deleted, is draft, open, in_progress, paused or in_review, and either depends on something unfinished or every path through its projects and groups is inactive. waiting_for names what. A task that is done or cancelled, or deleted, is not waiting, whatever it depends on; one that is done with an unfinished dependency carries a problem instead.

"Finished" means done or cancelled for a task, and ready or cancelled for a project. A deleted item holds nothing back either.

Neither word is a status, and neither can be set. Finish the cart page, and the payment form that depended on it is next for the following caller, with no step in between that could be forgotten.

What can I do now?

list_next_tasks answers it for whoever asks: the tasks that are next and are assigned to the caller or to nobody, the most important first. A draft is never listed. A group can be next like any task.

Listing starts nothing. A task is taken by setting it to in_progress, and of two callers who do that, one is refused.

Waiting for a group, or a project

In the picture above the launch waits for one task, the confirmation email. It could wait for the whole checkout instead: a task can depend on a single task, on a group or on a project, and the picture of a plan as a graph shows a launch that waits for a group. Depending on a group waits until the group itself is set to done or cancelled: one link stands for all the steps inside. Depending on a project waits until the project is ready or cancelled.

A task that depends on something unfinished cannot be started and cannot be finished. That is a rule, and the refusal lists what it is waiting for.

Why none of it is stored

A stored "ready" flag has to be kept right by every change that could affect it, in every task that depends on the one that changed. The day one update is missed, the flag lies. Vigile keeps only the facts, statuses and links, and works the rest out when it is read: next, waiting, the progress of a group or a project, and problems. The answer cannot disagree with the plan, because it is made from it.

Reference