Push changes from a field from project 1 to the same field on project 2

[Irina Lemus]

Hello and TIA!

I am trying to set up an automation rule that updates the field (due date) from project 1 (PPI) and updates the same field on project 2 (PCR) whenever a link exists that is either cloned by or blocked by.

Any ideas of what I might be doing wrong?

Here is the rule header

the trigger is set as

the if condition is set as. I had tried having both PPI and PCR in the JQL but it made no difference.

and how the rule is supposed to update after if finds a PCR ticket linked.

Here is the result: No actions performed.

[GNarsimhagowda - Empyra · Accepted solution]

Hi @Irina Lemus ,

I have tested this automation below and it is working for me, it is changing the due date of the linked issue. However, I have done certain changes to the rule.

• I have added branch for the linked issue 
• In the "edit issue action", I have added the field to copy from the trigger issue. 

[Irina Lemus]

@GNarsimhagowda - Empyra your recommendation worked backwards (from the other project) but it WORKED! Thank you so much for looking into this and for your help!!!

[Richard Scholtes]

Hi @Irina Lemus ,

so let me try to sum this up so you can check if I understood you correctly:

The rule checks the projects PPI and PCR.
It should recognize any ticket that has the field "due date" changed.

Those tickets should be checked if they have a ticket linked to them that is in project PCR and has the link types "is cloned by" or "is blocked by".

Then it should copy the content of the due date field from the trigger issue to the linked issue in project PCR.
Correct?

According to the screenshot of the audit log, trigger issue PPI-4695 did not have the correct relations to a PCR ticket.
What relations did it have if you open the issue PPI-4695?

[Irina Lemus]

Thank you so much for looking into this @Richard Scholtes !

Your understanding is correct. However, I was thinking of only changing the due date in the PPI project as opposed to having it synced both ways (it feels riskier). But I am okay to have it both ways if that simplifies this. I just don't want to maintain the same field in 2 projects.

To answer your question, the ticket PPI-4695 has PCR-10840 which is cloned from PPI-4695.

[Irina Lemus]

Here is another view if I update the due date on the PCR ticket and vice-versa (from the PPI)

I know the due date field exists in both...

and how it shows in PCR

[Richard Scholtes]

thanks for sharing the screenshots!
It may be possible that the automation user might not be allowed to access or change the value of the field. Can you check if the rule succeeds if you change the executing user to your own, assuming you would be allowed to change the due date manually?

[GNarsimhagowda - Empyra]

Hi @Irina Lemus ,

Try creating "Branch" for the Linked issue that might help!

Thanks.