Classification rules

Classification rules validate class assignments on tasks and time entries. They help catch missing or incorrect classifications before they become gaps in your reports.

This is an advanced feature, and it is entirely optional. Your reports are built on the classes you assign to tasks; rules only check that work afterwards, and a workspace without a single rule reports exactly the same figures. Rules start to pay off once your scheme has grown past what you can still check by eye — several classifications, dozens of classes, or a team where not everyone applies them the same way. If you are still setting up your first classification, read Classifications first and come back to this page later.

Rule types

Implication

“If any of these classes is assigned, then this other class should also be present.”

Use this when classes across (or within) classifications have a logical relationship. For example: “if any work package class is assigned, the R&D class should also be present.”

Exclusion

“If any of these classes is assigned, then this other class should NOT be present.”

Use this when certain classes are mutually incompatible. For example: “if R&D is assigned, Non-R&D should not be present.” Same structure as implication, but warns when the excluded class IS assigned.

At least one

“At least one class from this classification must be present.”

Use this to ensure a classification is never left empty. For example: every task must have at least one class from the “R&D Eligibility” classification.

Exactly one

“Exactly one class from this classification must be present.”

Use this when a classification is mutually exclusive. For example: a task should be either “R&D” or “Non-R&D” — never both and never neither.

Where warnings appear

Rules are evaluated wherever a set of classes is on screen — you never have to ask for a check.

• In a task’s Classifications dialog — open it from the tag icon on the Tasks page. Any rule the task’s current classes do not satisfy appears as a yellow warning below the list.
• While you edit those classes — in the Edit classifications dialog the warnings are recalculated as you tick and untick classes, so you can see whether a change fixes or breaks a rule before you save it.
• In a time entry’s detail dialog — the entry’s snapshotted classes are checked as soon as the dialog opens, and again as a manager changes them.

After you save in either dialog, a Changes saved confirmation lists the rules that are still unsatisfied. It closes on OK — reopen the task or the entry if you want to act on them.

All warnings are advisory only — they never block saves.

Creating a rule

1. Go to Classifications and click the Classification rules button.
2. Click New rule.
3. Choose the rule type (Implication, Exclusion, At least one, or Exactly one).
4. Fill in the type-specific fields:
   • Implication / Exclusion: enter a name, select trigger classes, then select the class that must — or must not — be present.
   • At least one / Exactly one: select the classification. The name is generated automatically.
5. Click Save.

Editing and deleting rules

• Implication and exclusion rules can be edited (pencil icon) to change the name, trigger classes, or implied/excluded class.
• Completeness rules (at least one / exactly one) cannot be edited — delete and recreate them instead.
• Any rule can be deleted (trash icon) with a confirmation dialog.

Rule validity

Rules can become invalid when the classes or classifications they reference are archived or deleted:

• Implication / Exclusion: invalid if the “then” class is archived/deleted, or if all “if” classes are archived/deleted.
• At least one / Exactly one: invalid if the referenced classification is archived/deleted.

Invalid rules are marked with a red “Invalid” badge and are skipped during evaluation.