Boolean condition

Build individual expressions to be evaluated.

Boolean conditions use all the features made available by the powerful expression parser. You add as many conditions to a rule as needed.

The boolean condition will either return true or false - and the actions configured for each condition will only be performed when the condition returns true.

Read more about boolean or logical expressions.

Boolean condition configuration

Below you will find a detailed description of each parameter needed to configure the condition.

Expression

Enter a logical expression that will be checked. Field codes and parser expressions can be entered as well.

A very common example would be a simple field value check:

%{trigger.issue.status} = "Open"

followed by an action: For example: Add comment "Please start work"

Adding additional conditions checking for other statuses and combining them with different actions is a common example of a nested condition rule.

Additional options

Stop the execution if the condition is met

If the condition is fulfilled (returns true), the execution of the rule will stop after the condition. All elements following the condition will not be executed.

Invert condition

When selected, the condition's logic will be inverted.

This option is really helpful if you have very complex expressions. Simply re-use an expression on a second condition and invert it instead of inverting / negating every statement inside the expression.

Use cases and examples

Title	Automated action	Label
Inherit value from parent in Advanced Roadmaps hierarchy	Update field action
Copy excerpted value from new comments	Update field action
Add links to the issues in a ScriptRunner Issue Picker field	Create issue link action Delete issue link action
Copy the parent issue comments to its sub-tasks	Add comment action
Send email when a field is updated	Send email action
Notify the assignee one week before the due date	Send email action
Prevent having the same assignee in two sub-tasks	Update field action
Close epic when stories are done	Transition issue action
Automatically close parent when all sub-tasks are done	Transition issue action	STAFF PICK
Create issue link when issue is created	Create issue link action
Add comment after seven days in the same status	Add comment action
Delete the attachments of an issue 30 days after closing it	Update field action
Add sub-tasks to an automatically created issue	Create issue action
Track issues mentioned in comments	Create issue link action
Resolve issues when all options of a checklist are checked	Transition issue action
Assign issues to your team during a transition	Assign issue action
Assign an issue to the last assignee on a transition	Assign issue action
Add sub-tasks to an issue on creation	Create issue action
Keep the status of parents and sub-tasks in sync	Transition issue action	STAFF PICK
Automatically close sub-tasks when parent is completed	Transition issue action	STAFF PICK
Re-open issue when a new comment is added	Transition issue action
Close stories when epic is done	Transition issue action
Automatically assign issues to your team	Assign issue action

If you still have questions, feel free to refer to our support team.

Content

Space Tools

Boolean condition configuration

Expression

Additional options

Use cases and examples