You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have created a flow that copies the fixversion from a child to its parent (being that an epic or another task).
It works as a charm, but I have one problem: If I have parent P1 with children C1 and C2, if I edit C1, the automation copies C1 fixversion(s) to P1, but when I edit C2, it deletes all the values already in P1 and copies C2 ones... is there a way to prevent the deletion?
This is what I have tried so far:
Thanks in advance
I am not sure if you're actually on cloud, because your automation interface looks different than the current one in cloud. But if you are, you should be able to change the edit type by clicking on the three dots and then "COPY" (red arrow):
After doing this, you can click on the text pointed to by the green arrow, where you should be able to select "Add to existing values". Hope this helps.
Hi @Michel Neeser , thanks for the answer.
You are right, I am not in the cloud, I am on data centre... sorry for the confusion.
I do have something similar, but it doesn't work:
Changing from "Set value" to "Copy from", I can set it only in this way:
Despite the log saying it triggered and ran successfully, I can't see anything happening to the epic, that stays empty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Daniele Cerfeda Please note that there is a difference between an epic as parent and a "standard" issue as parent. The automation rule differentiates between these two types. In your case, it seems to be an epic, so you would have to change the automation rule to this:
If you have a "standard" issue as parent, the automation rule looks like the one you originally posted:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michel Neeser thank you for pointing that out, but I am using precisely that :)
I am not sure what I am doing wrong, or how to debug in a better way...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Daniele Cerfeda I think setting your action to "Trigger issue" should solve the problem, as "Current issue" refers to the epic and not to the child issue:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michel Neeser I can't believe I haven't simply tried to click on the description to find that option I have been looking all around!
That works, thank you very much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.