Business rule conditions
Conditions determine when a business rule action is activated. If no condition is defined, the action is always activated. You can combine several conditions using AND or OR operators.
Define a condition
To define a condition, open the rule and click the Condition tab.
A condition can be based on one of the following: a field value, a count of related items (such as tests linked to a defect), whether the entity is new or being edited, or the current user's role.
Select field
Expand the Field list. The list contains entity fields, related item counts, Edit Mode, and Current User Role.
Entity fields
Select a field to base the condition on its value.
Single-value reference fields support cross-field conditions, enabling you to base a condition on the field's attributes. The fields are marked with a side arrow. Click the side arrow and select a field attribute. For example, on the Feature entity, you can select the Release > End date field, to prevent assigning features to old releases.
Edit Mode
Checks whether the entity is new or already exists and is being edited.
To check if new: Edit mode = New
To check if existing: Edit mode ≠ New
For supported entities, you can also check whether the entity is duplicated or split. For example, create a rule to clear certain fields when an entity is duplicated or split.
Current User Role
Checks whether the current user is assigned a specific role.
-
Use Original to evaluate the field’s value before the update that triggered the rule.
-
Use Current to evaluate the field’s value when the rule is triggered.
Related item count
Counts related items. Add a filter to count only related items that match specific criteria.
Example: Set a user story's Phase to Done when all its tasks are complete. In a Set Field Value rule, configure the condition as follows:
| Condition setting | Value |
|---|---|
| Entity | User Story |
| Field | Child task count |
| Filter | Phase is In Progress or New |
| Count comparison | = 0 |
The condition is met when no child task is In Progress or New. Set the rule action to change the story's Phase to Done.
Select an operator
Select an operator. Available operators depend on the field type.
The operator list is divided into Current and Original:
-
Use Current to evaluate the field's value when the rule is triggered.
-
Use Original to evaluate the field's value before the update that triggered the rule.
The following special operators are available, depending on the field type.
| Operator | Details |
|---|---|
| contains |
Checks whether the field contains a value you select from a list. The operator checks many-to-one relationships. |
| include |
Available for the Current User Role field. Checks whether the user is assigned to one of the selected roles. The operator checks one-to-one and equals relationships. |
| contains any/includes |
contains any checks many-to-many relationships. includes checks one-to-many relationships. For these operators, select Current User Teams and/or specific team names. These conditions can help apply different permissions to users in specific teams. |
| is empty | Checks whether the field is empty. |
| is modified | Checks whether the field changed from its original value. |
Filter operators
For a related-item count, select the Filter operator to count only related items that match your criteria. For details on defining filter criteria, see Advanced filters.
Set a value
Enter a value or select one or more values from a list. Multiple values are joined with an Or statement.
For user fields, you can enter [Current User] as a value. Add AND/OR expressions as needed.
A textual representation of the condition is displayed in the Description box.
Note:
-
You cannot set a user field for all workspaces in a shared space, as workspaces may have different users.
-
A condition evaluates to false if it uses a field that cannot be processed because the field does not exist or was removed.

