Vigile
SearchContents

How it works

Problems the plan finds in itself

A rule refuses a change that is wrong at the moment it is made. A problem is what is left when a change that was right makes something else wrong.

A problem: a task went on, and what it depends on was reopened Task WEB-008, the search box, depends on task WEB-007, the nightly index. WEB-008 is in review. WEB-007 was done and has been reopened, which is allowed. WEB-008 now carries the problem unfinished_dependency, and the project WEB carries the problem contains_task_with_problems. 1 · IT WAS DONE, THEN REOPENED WEB-007 Index all products every night status: done, and now open again Reopening is allowed. Nothing is refused. WEB-008 depends on it 2 · WHAT WENT ON IS FLAGGED WEB-008 Search box with suggestions status: in review unfinished_dependency depends on work that is not finished 3 · AND ITS PROJECT SAYS SO WEB Website relaunch contains_task_with_problems
The search box went to review while the nightly index was done. Then the index was reopened. Nothing was refused: reopening is allowed. The search box now says that it depends on unfinished work, and its project says that it holds a task with a problem.

How a problem comes about

Reopening a done task is allowed. So is restoring an existing task inside a done group, or marking a project ready while work in it is still open. Each can contradict something that was true a moment ago. New contents cannot be added to a done group: reopen the group first.

Vigile does not forbid them and does not quietly change other items to match. It says so, on the item that is now in question, for as long as it holds:

ProblemWhat is wrong
unfinished_dependencyA task is in progress, in review or done, but something it depends on is not finished: the dependency was reopened, restored or added afterwards.
inside_inactive_containerAn unfinished task has no active path into the plan because every path passes through a project or group that is not active.
done_with_unfinished_contentsA group is done, but tasks already inside it are not finished: one was reopened or restored afterwards.
depends_on_broken_projectAn unfinished task depends on a project that is marked broken.
project_brokenThe project is marked broken.
ready_with_unfinished_tasksThe project is marked ready, but tasks in it are not finished.
contains_task_with_problemsThe project holds tasks that have problems of their own.

A problem goes away by itself when its cause does: finish the dependency again, and the flag is gone at the next read.

Where problems show

  • A task or a project that an operation answers with, in short or in full, carries has_problems, and when it is true, problems: a code and a sentence for each. The items named under links and blocking do not.
  • list_tasks and list_projects take has_problems to list only those.
  • On the page, a task's card and a project's card with a problem carry a warning, the counts of the board say how many items have problems and show only those when chosen, and the panel of the item says what is wrong.
A task in review whose dependency was reopened. The panel says that its status is in_review but it depends on work that is not finished. Behind the panel, the card of its project carries a warning mark.A task in review whose dependency was reopened. The panel says that its status is in_review but it depends on work that is not finished. Behind the panel, the card of its project carries a warning mark.

A problem is not damage

Problems are about the plan: statements in it that no longer fit together. They are worked out from sound data.

Nor is a problem a judgement of the plan. Work in no group, or too much started at once, contradicts nothing and is not flagged: the shape of the plan shows it to whoever looks.

Damage is something else: a record that cannot be read, a link that leads nowhere. That is what the doctor looks for when it checks that the graph is consistent.

Reference