-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
Component/s: Action - Issue Actions
-
Severity 3 - Minor
Issue Summary
Smart values are not working as expected
Steps to Reproduce
- Create a custom field of any type, say Select List (single choice), and add it to a screen of a JSM project. Add options Yes and No to this field.
- Create another field of Assets objects type and add it to a screen.
- Create an issue and add values in the fields.
- Select No in the first field.
- Select any object in the second field.
- Create an Automation rule to print the values of the above fields.
- First Log action should contain {{not(issue.customfield_XXXXX.value.equals("Yes")}} Here, XXXXX represents the ID of the first field.
- The second Log action should contain {{issue.customfield_XXXXX.Name.equals("<object_name>")}} Here, XXXXX represents the ID of the second field and <object_name> is the name of the Object selected in the second field.
- Add another Log action with smart value {{and(not(issue.customfield_XXXXX.value.equals("Yes")),issue.customfield_XXXXX.Name.equals("<object_name>"))}}
- Run the rule.
Expected Results
All three values should be true.
Actual Results
The first two values are true while the last value is false:
Workaround
Create a rule with separate IF conditions to get the desired output.