Comparing the fixVersions of an issue to the fixVersions of linked issues

[Richard A. Michaels]

I have an issue which is the control document which list all the engineering project issues which are contained in a deployment.  The engineering project issues are linked to the control document.  

I'm using two fields to determine if an action should be taken against the linked issue based on two fields, Environment and fixVersion.  Both fields exist on the control document issue and the linked issues.

I am able to match the environments since it is the same exact multi-select field, however when I attempt to compare the {{issue.fixversions.name}} to  {{triggerissue.fields.fixversions.name}}, the two values are not the same.

Within the automation, I've used the Send Slack Message step to print out the values of the smart values before and after the compare.  The before step executes but the after step does not execute because the compare doesn't see the values as the same.

[Bill Sheboy]

Hi @Richard A. Michaels 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

What you describe could occur if there are multiple values in the Fix Version field and they were added / changed in different sequences for the issues compared.  Seeing the specifics of your rule, and perhaps example issues, may help to suggest solution approaches.

Kind regards,
Bill