Does "FixVersions" field is limited to changes from the advanced edit?

[Gilad Waldman]

Hello, 

Built an automation that will automatically add fixversion when a ticket is deployed into a new version. 

The flow works great but what i can see that the automation always adds 2 values and if there are more than 2, it takes the last ones.

I wonder if there is a limitations on that? if not, i can share the automation for better visibility on my flow.

Thanks.

[Gilad Waldman]

Thanks for the response @Bill Sheboy
I manage to build this automation in multiple ways and each time i recived the same result - only the last two items are being added into "Fix Versions".

On the attached image, the result will be get(1) and the new customfield (which i already created a version for) and the oldeset value (get(0)) is deleted. 

[Bill Sheboy]

First thing, please stay with one thread when responding.  That will help others looking at this question in the future know if there are multiple solution approaches.  Thanks!

Next, you are not showing your entire rule, and so the context of where, how, and on which issue is being edited is unclear.  Please post an image of your entire rule for context, in one single image.

Finally, when using the Edit Issue action, a field should only be updated one way: with the dropdown list selection or using advanced edit with JSON.

Your rule is doing both in the same action, and so I would expect the results to be unpredictable as the updates collide.  Please unselect the Fix Versions field from the dropdown list and then re-test your rule.

[Bill Sheboy]

Hi @Gilad Waldman 

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...

Fix Versions is a list field, and contain multiple values.  If multiple values are being added, either the source / smart value has multiple values or perhaps the rule is triggered multiple times.  Seeing the details will help identify the cause.

Kind regards,
Bill