Automation: Issue Linked triggerIssue smart variable

[Keiran]

We have a process where:

1. Issue-A is created via the portal
2. Automation fires an email to an external party with Issue-A in subject
3. Reply via email is received creating Issue-B
4. Automation links Issue-B -> Issue-A
5. Copy info from Issue-B into Issue-A comment

I'm currently trying to automate copying information from Issue-B into a comment (5) on Issue-A in isolation, eventual aim being to chain them if that's possible.

If I manually trigger a link of Issue-B to Issue-A the automation fires and populates the comment:

• Select Issue-B
• Link - relates-to - Issue-A
• Comment added to Issue-A

However the {{triggerIssue...}} fields don't appear to be accessing the data in Issue-B.

Here's the rule:

And the resulting comment generated on Issue-B:

TriggerIssue: Issue-B

Issue: Issue-B

Reported by:

Summary: Summary of Issue-B

Content:

Any help would be appreciated.

[Fabian Lim · Accepted solution]

Hi @Keiran ,

You need to branch out to issue A a after is linked. More details here: https://support.atlassian.com/cloud-automation/docs/what-is-rule-branching/

I would also use another link relationship as "relates to" is the same name for both inward and outward. 

[Keiran]

Thank you for the pointers.  I have the rule working in isolation now.

I'm attempting to merge the independent rule into a larger flow that performs the link:

Is this possible?  Alternatively can the outcome of an automation trigger other automations (it doesn't seem to)?

[Keiran]

Never mind, I found the magic checkbox:

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Can-I-use-automation-rule-to-trigger-another-automation-rule/qaq-p/912010