Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira automation: copy fixversion to parent

Daniele Cerfeda May 10, 2023

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:

Immagine 2023-05-10 183303.jpg

 

Thanks in advance

1 answer

1 accepted

1 vote
Answer accepted
Michel Neeser
Community Champion
May 10, 2023

Hi @Daniele Cerfeda

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):

dots-2.png

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.

Daniele Cerfeda May 11, 2023

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:

 

Immagine 2023-05-11 141644.jpg

 

Despite the log saying it triggered and ran successfully, I can't see anything happening to the epic, that stays empty

Immagine 2023-05-11 142123.jpg

Michel Neeser
Community Champion
May 11, 2023

@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:

Automation_-_Jira-3.png

If you have a "standard" issue as parent, the automation rule looks like the one you originally posted:

Automation_-_Jira-2.png

Daniele Cerfeda May 12, 2023

@Michel Neeser thank you for pointing that out, but I am using precisely that :)

Immagine 2023-05-12 101328.jpg

 

I am not sure what I am doing wrong, or how to debug in a better way...

Michel Neeser
Community Champion
May 12, 2023

@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:

Automation_-_Jira-2.png

Daniele Cerfeda May 15, 2023

@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!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events