nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Fabian Weber

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:

Trigger: Bug is created in Jira Space
Step 1: Find Test Work items linked to the Bug via "is created by" link type
Step 2: For each Test found, find MigObjects linked via "tests" link type
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"

Accepted answers

Fabian Weber

✅ Resolution acquired!

After a lot of configuration changes and testing we got a solution – thanks a lot for the support, especially @Rudy Holtkamp !

The key points that made the automation work:

Use the correct link types consistently across your branches:
- Bug → Test: created by
- Test → MIGObject: tests
Ensure that your branch configuration matches your desired exact link types, otherwise related issues won’t be found.
Pass the originating issue correctly via the webhook using:
```
?issue={{issue}}
```
This was essential to transfer the context between the two automation rules.
Use a two-step automation approach:
1. First rule: Trigger on Bug creation → call webhook
2. Second rule: Receive webhook → traverse linked Test issues → link corresponding MIGObjects back to the Bug

✅ Result:
When creating a Bug and linking it to a Test, all MIGObjects linked to that Test are automatically linked to the Bug as well.

Here are some Screenshots of the two Automations for a better understanding:

Automation 1:

Automation 2.png

Automation 2: Automation 1.png

💡 Maybe this helps someone facing a similar setup with cross-linked issue structures and webhooks.

All comments

Rudy Holtkamp

Hi @Fabian Weber ,

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

Create an automation 'flow 1'

Trigger 'Incoming webrequest'
Add a log action: "webhookData: {{webhookData}}"
Save the flow (we get back to it later), but do copy the Webhook URL (e.g. https://api-private.atlassian.com/automation/webhooks/jira/a/226b29aa-455f-46d7-9e00-1dee77366bdc/019ef46e-ee32-768c-9d36-9385d144135f) & Secret (e.g.caaeef84169f56d763e47df691a6a04cbdb674bb) (or keep it close by to copy it later).

With your flow:

Trigger: Bug is created in Jira Space
I think you know how to do this
Find Test Work items linked to the Bug via "is created by" link type
Create a branch on linked work items, with link types 'is created by'
In the branch:
- Add a log: Test work item: {{issue}}
- Add a 'Send web request', use the webhook url with ?issue={{issue}} added to the URL of flow 1. E.g. https://api-private.atlassian.com/automation/webhooks/jira/a/226b29aa-455f-46d7-9e00-1dee77366bdc/019ef46e-ee32-768c-9d36-9385d144135f?issue={{issue}}
  Use Post
  Use Custom Data: { "originalIssue":"{{triggerIssue}}"}
  Use X-Automation-Webhook-Token as the header key and the Secret (e.g. caaeef84169f56d763e47df691a6a04cbdb674bb) as value
Save 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

Fabian Weber

Hello Rudy,

thanks a lot for your dedication and quick answer!

I think I already implemented the two automations so far.

Is this how you thought of the result?

Flow 1 .png 2 Automation .png

Fabian Weber

fyi: When you said "Use X-Automation-Webhook-Token as the header key" - where did you find the token exactly?

I just used the webhook url for it. Please correct me if there is a better solution.

Rudy Holtkamp

Hi @Fabian Weber ,

For the first picture the branch should also be a 'For linked work items' not a branch on JQL. The rest looks like I intended.

Fabian Weber

✅ Resolution acquired!

After a lot of configuration changes and testing we got a solution – thanks a lot for the support, especially @Rudy Holtkamp !

The key points that made the automation work:

Use the correct link types consistently across your branches:
- Bug → Test: created by
- Test → MIGObject: tests
Ensure that your branch configuration matches your desired exact link types, otherwise related issues won’t be found.
Pass the originating issue correctly via the webhook using:
```
?issue={{issue}}
```
This was essential to transfer the context between the two automation rules.
Use a two-step automation approach:
1. First rule: Trigger on Bug creation → call webhook
2. Second rule: Receive webhook → traverse linked Test issues → link corresponding MIGObjects back to the Bug

✅ Result:
When creating a Bug and linking it to a Test, all MIGObjects linked to that Test are automatically linked to the Bug as well.

Here are some Screenshots of the two Automations for a better understanding:

Automation 1:

Automation 2.png

Automation 2: Automation 1.png

💡 Maybe this helps someone facing a similar setup with cross-linked issue structures and webhooks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

xray

jira

webhook

automation

jira-automation

linking

branches