-
Suggestion
-
Resolution: Unresolved
Problem Definition
With a Rule structured like so, where <Smart Value> has a value, and <Field> starts as empty:
- IF Condition > <Smart Value> is Not Empty
- Edit Issue Action > <Field> is set to <Smart Value>
- Re-Fetch Issue Data Action
- IF Condition > <Field> is Empty
- <Actions>
Both IF Conditions can be passed, because even if the first IF Condition sets the Field to a value, then Re-Fetches Issue Data, the second IF Condition will see that the Field is Empty even though it is no longer Empty, since the Re-Fetch is within the prior IF Condition.
Suggested Solution
Have Re-Fetch Issue Data within a Condition take effect outside of it.
i.e. in the above example, have the first IF Condition's Re-Fetch Issue Data enable the second IF Condition's checking to recognize that <Field> has a value now.
Workaround
Place the Re-Fetch Issue Data Action outside of IF Conditions.
- relates to
-
JIRAAUTOSERVER-1003 Make re-fetched issue data available to conditions outside of an if block in automation rules.
- Gathering Interest