Automation to update children of Epic is reporting success, but not working

[Alex Smith]

I created the following automation following some examples I found on this forum. The automation aims to set the fixed version on all child tickets of an epic to the same value as the parent epic.

As you can see from the log, I'm saving the Epics fixVersion in a variable and logging that variable to confirm it worked. Then I start the For: Stories to loop over the child tickets. I'm again logging the value in epicFixVersion. Finally, it logs that it has successfully updated all of the tickets in the epic.

I'm setting the Fix Version with this action:

The logs look good. The automation seems like all the others I've seen, but the child tickets aren't changed. 

[Kai Becker · Accepted solution]

Hi @Alex Smith 

welcome to the community and thanks for your question.

Actually there is an easier way than creating a variable and copy values.

You can just edit the issue field in your loop an copy over the value from the trigger issue:

Hope this helps 🙂

[Bill Sheboy]

Hi @Alex Smith -- Welcome to the Atlassian Community!

Yes, and...to the answer from Kai:

The reason your rule does not work as you expect is created variables are text, and you have stored a list of multiple versions in it.  That got converted to a comma-separated values list...but of only the version id values, not all of the version information.  That was visible when you logged the created variable.

To use that variable in the issue edit, you would need to split them apart and then add them using a JSON edit.

The way Kai described is much simpler. 

Remember to decide if you want to replace or add to the stories in the epics: to replace, clear the "Add to existing values" checkbox in the edit.

Kind regards,
Bill

[Alex Smith]

Thank you for the explanation Bill! I like understanding why things don't work as expected, so I appreciate that! 

[Alex Smith]

Thank you! Works great. 

[Marc - Devoteam]

Hi @Alex Smith 

Seems you have used part of I rule I presented on another topic in the community.

The setup of that rule has very different requirements.

The requirement you have is a simple one, as explained by @Kai Becker 

[Wendy Hamlin]

While looking for something similar I came across this thread. Just had to say - love the profile pic!