Automation Rule to Add FixVersion to Issues is not working as expected

[Ledith_Harrison]

I have the following automation rule set up in our project (company managed)

I am expecting that any issue in the Pre-Readiness column where the fixVersion field is empty will update with the newly created release.  I have seen this rule work as expected when there is only issues in that status with the fixVersion field empty.  When there is a mix of issues with and without the fixVersion field populate the rule audit is showing the rule ran successfully, but the fixVersion field is not updated with the new version.  What corrections do I need to make to resolve the issue so that issues that are in the Pre-Readiness column will update accordingly.   (I do not want to overwrite existing fixVersion where there is a value that is present.  I only want to update when the fixVersion field is empty.)  

I am hoping someone can provide some assistance.  

Ledith H.

[Kalyan Sattaluri · Accepted solution]

Hello @Ledith_Harrison 

Please share the screenshot of the "Edit Issue" section of the rule. Are you using the {{version.name}} smart value like below.

[Ledith_Harrison]

Kalyan, upon checking that field that field was null.  Once I populated it, the automation worked as expected based on my current use. 

Thank you for your feedback.

Ledith

[Bill Sheboy]

Hi @Ledith_Harrison 

To add to the existing fix version values, your edit action will need to use advanced edit with JSON rather than the dropdown field list, to "update" with an "add": https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions

The reason is the out-of-the-box option to add versions to an issue are based on a source issue's field, and that is not the case for your trigger: Version Created.

Kind regards,
Bill

[Ledith_Harrison]

Thank you Bill for your feedback.  I will see if this solves my issue.