Automation: Issue Linked triggerIssue smart variable

Keiran May 20, 2022

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:

trigger-issue.png

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.

1 answer

1 accepted

4 votes
Answer accepted
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2022

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 May 20, 2022

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:

link-then-branch.png

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

Like Fabian Lim likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events