-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
7.4.2
-
None
-
Severity 3 - Minor
Issue Summary
When using the OR smart values on the Fix Version field, it doesn't return the right results.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create a new issue and add the Version 1.0 value to the Fix Version field.
- Create a new Automation rule with "Manually triggered" and add the "Edit Issue" on the action.
- Choose to update the Description field with the syntax below.
- Paste the smart syntax in the rule actions:
* issue.fixVersions.name.equals("Version 1.0"): {{issue.fixVersions.name.equals("Version 1.0")}} * or(issue.fixVersions.name.equals("Version 1.0"), false): {{or(issue.fixVersions.name.equals("Version 1.0"), false)}} * or(issue.fixVersions.first.name.equals("Version 1.0"), false): {{or(issue.fixVersions.first.name.equals("Version 1.0"), false)}}
- Publish the changes.
- The results we get is this:
Expected Results
Based on the OR logic:
or(issue.fixVersions.name.equals("Version 1.0"), false)
When comparing true or false, we should get true instead of false.
Actual Results
The results returned false instead comparing true OR false logic.
Workaround
Add a .first syntax:
or(issue.fixVersions.first.name.equals("Version 1.0"), false)
- relates to
-
![[JIRA Server (Bulldog)]](/images/icons/generic_link_16.png "[JIRA Server (Bulldog)]")
A4J-3005
You do not have permission to view this issue
[JIRAAUTOSERVER-481] When using OR syntax in FixVersion field, it doesn't return correct results
displayed result of
{{issue.fixVersions.name.equals("Version 1.0")}}
is iteration over all names in the collection, that's why for one element collection the displayed text looks like single result.
To properly observe difference please check following smart value:
This is original one: * issue.fixVersions.name.equals("v1.0.0"): {{issue.fixVersions.name.equals("v1.0.0")}} * or(issue.fixVersions.name.equals("v1.0.0"), false): {{or(issue.fixVersions.name.equals("v1.0.0"), false)}} * or(issue.fixVersions.first.name.equals("v1.0.0"), false): {{or(issue.fixVersions.first.name.equals("v1.0.0"), false)}} Iterating through fixVersions {{#issue.fixVersions}} * current version name: *{{name}}* ** name.equals("v1.0.0"): {{name.equals("v1.0.0")}} ** or(name.equals("v1.0.0"), false):{{or(name.equals("v1.0.0"), false)}} {{/}}
For the Issue where just single fix version is set the result is:
In case of the issue where multiple fix versions are set, the result is
Regards
Daniel Ramotowski
Wait a second.
In bug report it is stated that
issue.fixVersions.name.equals("Version 1.0")
returns true, not false, as you say.
So,
or(issue.fixVersions.name.equals("Version 1.0"), false)
should return true.
The fixVersions issue field is a list of values, so the example
or(issue.fixVersions.name.equals("Version 1.0"), false)
that returns false works as expected
This is because comparing list of values to the string "Version 1.0" returns false in this call:
issue.fixVersions.name.equals("Version 1.0")
then or(false, false) return false which is correct.
More about accessing list values:
https://confluence.atlassian.com/automation/lists-993924868.html
https://confluence.atlassian.com/automation/working-with-lists-993924631.html
Regards
Daniel Ramotowski
I see now. I was thinking for some reason that this single fix version will be casted to string and will be compared as a string.