Linking then copying custom field data from one issue to another

Question

Hello, I am trying to create a "split process" of sorts in which:

* Person 1 submits a request type ticket creating Issue A.
* I then have an Automation which emails Person 2 with a direct link to complete a different request type ticket creating Issue B in the same project.

I am now trying to create the next automation intending for:

* Issue B to link/merge into (whatever makes the most sense) Issue A based on the same custom field input (unique number) and then for the custom field data from Issue B to copy over into Issue A, as I have also put the custom fields for Person 2 inside the request form/type for Person 1 but have them hidden available for the information to be copied over.
* My intent after this is to take the information from Issue A (which would now have data from both issues) and email stakeholders with this custom field data. I am pasting my current automation which begins after the form in Issue B is submitted...

Trudy P Claspill · Answer

Did my previous response give you the information you need to solve this, or do you still have outstanding questions?

Bella DePourcq · Answer

Ah okay yes, I have the same custom field, "requisition #", in both Issue A and Issue B which needs to be the same response for the automation to link. I was having trouble creating a JQL search or condition that could search for/within the Issue Type A for this custom field response and then link if the response in Issue B field was the same.

Trudy P Claspill · Answer

Hello @Bella DePourcq

Welcome to the Atlassian community.

Do I understand correctly that you expect this rule to run when Issue B is created?

And this rule is intended to copy data from Issue B to Issue A?

If I have understood correctly:

* Is there anything in Issue B that identifies Issue A when Issue B is created? Is the Issue A key part of the data submitted with Issue B as it is created?
* Issue B must have some way of identifying Issue A prior to the triggering of this rule, whether that is by already have the Issue A key somewhere in the data of Issue B, or being able to execute a JQL statement with criteria that would find the specific Issue A that should be related to Issue B.
* Then, within this rule, you would need to use a Branch (For Each) action to change the focus of the rule activity to Issue A.
* Within that branch you would execute the Link Issue and Edit Issue actions.

Example: