We have a process where:
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:
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-BIssue: Issue-BReported by:Summary: Summary of Issue-BContent:
Any help would be appreciated.
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.
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)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Never mind, I found the magic checkbox:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.