Conditions provide the necessary features to turn a rule into a structured vehicle to automate even the most complex processes.
Conditions can limit overall rule processing to specific issues meeting condition criteria, or define different kinds of processing depending on issue content.
Conditions can be added to triggers, selectors, and even conditions to turn them into nested conditions.
Think of a condition as an "IF - THEN" clause. Nested conditions can act as "IF -THEN -ELSE" clauses.
ADD IMAGE FROM OVERVIEW PAGE
Available automation conditions
The following automation conditions are currently available:
The options actually available depend on which other elements (triggers and/or selectors) have been selected upfront.
Nested conditions
Explain, screenshot, screencast ??? Jona Ittermann
Combining multiple similar conditions with different actions is the most common use case for a nested condition.
- Condition: If it rains
- Action: Take umbrella
- Condition: If it is sunny
- Action: Maybe take umbrella to provide shade but definitely wear short pants
- Condition: If it snows
- Action: Take winter jacket
- Condition: If it neither rains, nor snows nor anything else
- Action: Turn on weather channel
If you still have questions, feel free to refer to our support team.
