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
Use cases
Use case | Automated action | Use case description | Complexity |
---|---|---|---|
Add sub-tasks to an issue on creation | Automatically create 3 sub-tasks - Documentation, Marketplace and Newsletter. | BEGINNER | |
Track issues mentioned in comments | Automatically link issues based on comments. | ADVANCED | |
Resolve issues when all options of a checklist are checked | When all options of a custom checkbox field are ticked, the issue is resolved and transitioned to DONE | INTERMEDIATE | |
Keep the status of parents and sub-tasks in sync | When an issue is being rejected, all sub-tasks will be transitioned to the REJECTED status as well - automatically. | BEGINNER | |
Assign an issue to the last assignee on a transition | When an issue is transitioned to the DRAFT status, the issue will be automatically re-assigned to the last assignee from the project role "Developers". | BEGINNER |
If you still have questions, feel free to refer to our support team.