Copy field to parent project.

[Francisco Navarro]

Dear community,

I have an automation that seeks to be able to "copy" the data from a drop-down list field (it is in an epic) and paste it into another project linked to this one through the "parent", the destination field is called the same way (Site Type).

I have been trying to get this done for a few days now and I have not been able to, in the automation log it appears that it does it but when I check the ticket of the parent related to the epic, the field appears empty, can you help me figure out where I am failing? I attach an image of the log and the rule.

[Florian Bonniec · Accepted solution]

Hi @Francisco Navarro 

Could you share your current automation rule ?

Regards

[Francisco Navarro]

Hi Florian,

Is this useful to you?

[Florian Bonniec]

How did you configure the Edit Issue field action ?

[Francisco Navarro]

@Florian Bonniec 

[Florian Bonniec]

Hi

You should use {{triggerIssue.Tipo de sitio}} not {{issue.Tipo de sitio}}.

When you do the branching issue become the Epic so you copy nothing to teh field.

Regards

[Francisco Navarro]

Florian,

Perfect¡, this fixes the problem. It works now, thank you very much!

[Atlass Monster]

Hi, I tried to replicate your automation but I get the same result as you do, the parent that is of another project have been edited according to the logs.

But!

With this alternative writing I got the data to appear at least in the issue history;

[Francisco Navarro]

As you say, the log records that it does something... but I don't see anything reflected in the linked project.

I don't know if it's a jira issue or something I'm not seeing.

[Atlass Monster]

I too believe that is some kind of bug. My issue history of the parent issue shows changes, not the field did not changed even once. The only logical explanation is some kind of problem on the Atlassian side of mess.