nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira automation: copy fixversion to parent

unknown

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

Accepted answers

Michel Neeser

Hi @[deleted]

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.

All comments

Michel Neeser

Hi @[deleted]

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.

unknown

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

@[deleted]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:

unknown

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation