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.
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:
| Problem | What is wrong |
|---|---|
unfinished_dependency | A 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_container | An 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_contents | A group is done, but tasks already inside it are not finished: one was reopened or restored afterwards. |
depends_on_broken_project | An unfinished task depends on a project that is marked broken. |
project_broken | The project is marked broken. |
ready_with_unfinished_tasks | The project is marked ready, but tasks in it are not finished. |
contains_task_with_problems | The 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 underlinksandblockingdo not. list_tasksandlist_projectstakehas_problemsto 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 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
- The model: the problem codes.
- Statuses and the rules of moving: what is refused outright.