Conditions
Conditions are optional. They restrict a rule so it only runs in specific cases. Each condition compares a field with an operator and — for most operators — a value.
You can add several conditions. All of them must be true for the rule to run (logical AND).
For how to add conditions in the editor, see Creating a rule.
Operators
The same operators are available in every area. Whether a value input appears depends on the operator.
| Operator | Meaning | Needs a value? |
|---|---|---|
| Equals | The field exactly matches the value. | Yes |
| Not equals | The field does not match the value. | Yes |
| Contains | The field contains the value. | Yes |
| Does not contain | The field does not contain the value. | Yes |
| Is empty | The field has no value. | No |
| Is not empty | The field has any value. | No |
| Greater than | The field is greater than the value. | Yes |
| Less than | The field is less than the value. | Yes |
| Starts with | The field begins with the value. | Yes |
| Ends with | The field ends with the value. | Yes |
Before-change operators
These six operators compare a field's value as it was before the change that triggered the rule. They let you react to how a value changed — for example, only run when the status changed away from a specific value.
| Operator | Meaning | Needs a value? |
|---|---|---|
| Before change equals | The previous value exactly matched the value. | Yes |
| Before change not equals | The previous value did not match the value. | Yes |
| Before change contains | The previous value contained the value. | Yes |
| Before change does not contain | The previous value did not contain the value. | Yes |
| Before change is empty | The field had no value before the change. | No |
| Before change is not empty | The field had any value before the change. | No |
The before-change operators appear in the operator list only when the rule's trigger is the …updated trigger of its area (for example Task item updated or Project updated). They are not available for …status changed, …marked as done, or any other trigger.
Condition fields
The fields you can check depend on the area. The Type determines the value editor (text, number, date, yes/no, or a selection).
Person fields such as Created by, Changed by, Performed by, Manager, or Customer are compared as display names, not as email addresses or IDs. Fields that can hold several entries — Team, Categories, Contributors — contain all entries as one text. Use Contains (or Is empty / Is not empty) for these instead of Equals.
For person-name fields, text comparisons are case-insensitive. For example, max mustermann and Max Mustermann match.
Tasks
| Field | Type |
|---|---|
| Task | Text |
| Description (Task) | Text |
| Task Status (Name) | Selection or text (typed status name) |
| Assigned to (Name) | Selection |
| Project name | Text |
| Division name | Text |
| Effort (Task) Hours | Number |
| Booked time (hours) | Number |
| Task Completed | Yes/No |
| Start | Date |
| Due Date | Date |
| Contributors | Text |
| Created by | Text |
| Changed by | Text |
| Created on | Date |
Projects
| Field | Type |
|---|---|
| Project name | Text |
| Project number | Text |
| Project status | Text |
| Division | Text |
| Start date | Date |
| End date | Date |
| Is archived | Yes/No |
| Is request | Yes/No |
| Risk score | Number |
| Size score | Number |
| Value score | Number |
| Customer | Text |
| Manager | Text |
| Team | Text |
| Categories | Text |
Budgets
| Field | Type |
|---|---|
| Budget name | Text |
| Budget type | Selection |
| Budget date | Date |
| Amount | Number |
| Consecutive number | Number |
Documents
| Field | Type |
|---|---|
| File name | Text |
| File type | Text |
| Folder path | Text |
| State | Text |
| Created by | Text |
| Changed by | Text |
| Created on | Date |
| Modified on | Date |
Time entries
| Field | Type |
|---|---|
| Name | Text |
| Description | Text |
| Start | Date |
| End | Date |
| Duration in minutes | Number |
| Billable | Yes/No |
| Billed | Yes/No |
| Performed by | Text |
| Created by | Text |
| Changed by | Text |
| Project name | Text |
Planning
| Field | Type |
|---|---|
| Name | Text |
| WBS code | Text |
| Progress | Number |
| Start | Date |
| End | Date |
| Is milestone | Yes/No |
| Is grouping | Yes/No |
| Duration in hours | Number |
| Work amount in hours | Number |
Line items
| Field | Type |
|---|---|
| Description | Text |
| Quantity | Number |
| Unit | Text |
| Price per unit | Number |
| Amount | Number |
| Is billed | Yes/No |
| Is billable | Yes/No |
| Group | Text |
Risks
| Field | Type |
|---|---|
| Name | Text |
| Description | Text |
| Likelihood | Number |
| Impact | Number |
| Score | Number |
People
| Field | Type |
|---|---|
| Name | Text |
| First name | Text |
| Last name | Text |
| Display name | Text |
| Company | Text |
| Text | |
| Phone | Text |
| Mobile | Text |
| Position | Text |
| Department | Text |
| Street | Text |
| ZIP code | Text |
| City | Text |
| Country | Text |
Organizations
| Field | Type |
|---|---|
| Name | Text |
| Customer number | Text |
| Street | Text |
| ZIP code | Text |
| City | Text |
| State | Text |
| Country | Text |
| Domain | Text |