Make a task depend on a value

A “condition” makes a task apply only when one of the project's values passes a test, for example only when the client approved the appeal. You do it in two parts, in a draft: add the “field” in Fields, then add the condition to the task in Tasks. You need to be a department manager or a company administrator.

• You need a draft. To change a published template, revise it first: Change a published template.
• Decide the test: which value, how to compare it, and with what. The comparisons for each type are in Field types and comparisons.

1. 1.
   On the template's page, select Edit on the draft.
2. 2.
   Select Fields in the left menu. Under Add a field, type the Name, choose the Type, and select Add field. For a Choice, type each option in Options and press Enter.
3. 3.
   Select Tasks in the left menu. Under the task, select Add a condition.
4. 4.
   Choose the field, then the comparison, then type or choose the value. The test saves as soon as it is whole.

   Template editor · Tasks · a task's conditions

   Example · sample data

   Only when

   2 conditions

   Edit

5. 5.
   For another test, select Add a condition again. The task applies only when every test passes.
6. 6.
   Select Done.

Under the task, the row shows Only when and how many conditions it has. After you publish, a new project shows the task as Not applicable on the project's page until its values pass every test. Every value starts empty, so a task with a test usually starts that way. While the value it tests is empty, its card in the Work panel says Undecided. When a value is entered and a test still fails, the card says Not applicable.

• There is no Add a condition: the version has no fields yet, so Tasks shows one line with a link to Fields. Or the version is published: it shows Show and can only be read.
• A line in red under the value says what is wrong, for example “Enter a number.” or “Choose a value.” Fix the value; the test is not saved until it is whole.
• A choice field says “This field has no options yet. Add them under Fields.” Give the field its options first.
• A field is not in the list: it is ticked For each task on Fields. A condition tests only the fields that belong to the project.

On a running project, see Why a task is “Not applicable”.