Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I set up a nested Jira Automation rule to automatically link Bugs to MigObjects via Tests in

Fabian Weber
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 23, 2026

Hello everyone,

I need assistance setting up a complex Jira automation rule in our Jira Space using Xray. Despite having the detailed specification and attempting manual configuration, I'm unable to successfully implement structure required for this workflow. I'm open to all possible ways to have a solution (like nested branching or lookup issues etc.)

Business Requirement

We need an automation rule that automatically creates Work item links between Bugs (Xray Work type) and MigObjects (work type) through their relationship with "Test" (Xray Work type) when a new Bug is created.

Workflow Logic generally:

  1. Trigger: Bug is created in Jira Space

  2. Step 1: Find Test Work items linked to the Bug via "is created by" link type

  3. Step 2: For each Test found, find MigObjects linked via "tests" link type

  4. Step 3: Create "relates to" links between the original Bug and each discovered MigObject

Goal: You can see all related (in a wider understanding) in the Screen of "MigObject"

1 answer

1 vote
Rudy Holtkamp
Community Champion
June 23, 2026

Hi @Fabian Weber ,

I think (not tested myself) you can do this by:

Create an automation 'flow 1'

With your flow:

Back to flow 1

When this flow is triggered you have the original issue (the bug) in the smart value {{webhookData.originalIssue}} and the Test Work item in {{issue}}. If more test work items were found in your flow then flow 1 will be triggered for each of these. Now we need to branch in this rule again to find all MigObjects 

  • Create a branch on linked work items, with link types 'test'
  • In the branch
    • Add action 'Link work items'
      Choose 'relates to'
      Use smart value {{webhookData.originalIssue}}

Now your MigObject is linked to the bug

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events