How to trigger Jira Automation when an Xray Test Run changes status in the new "Spaces" UI?

[Lena Wong]

Hi everyone,

I am trying to create a basic automation rule in Jira Cloud using the new "Spaces/Work" interface.

My goal is simple: When the first Test Run within a Test Execution changes from "TO DO" to any other status (EXECUTING/PASS/FAIL), I want the parent Test Execution issue to transition from "To Do" to "In Progress".

However, when I go to Space Settings > Automation > Create flow, and search for "Xray" or "Test run" in the "Add a trigger" sidebar, no results appear ("No triggers match your search").

1. Is the native Xray trigger ("Test Run Status Changed") compatible with this new Jira Automation interface?
2. Do I need a specific administrative permission or global setting enabled for the Xray triggers to show up in the Automation project scope?
3. Is something like the requirement possible to automate in JIRA / XRay?

Thanks in advance!

[Viswanathan Ramachandran]

Hi @Lena Wong 

You can refer to this article - https://community.atlassian.com/forums/Automation-articles/Navigating-Test-Execution-Workflows-A-Beginner-s-Guide-to-Jira/ba-p/2606780

additionally https://getxraydocs.atlassian.net/wiki/spaces/XRAY770/pages/48956090/Integrations could be handy. 

Do not hesitate to contact X-ray support if you need something else. 

[Germán Morales]

Hi @Lena Wong , none of those three things is a permissions or UI problem, it's architectural: a Test Run is not a Jira issue, Xray treats it as a virtual entity that only Xray's own API knows about, so Jira Automation, which only listens to issue events, has nothing to hook into there. That's true in the classic interface and in Spaces alike.

• There's no native "Test Run Status Changed" trigger to find, it doesn't exist in Jira Automation at all.
• No setting or permission brings it back, the empty search result is expected behaviour, not a configuration gap.
• What you can automate is one level up: the parent Test Execution is a real Jira issue, so trigger on a field value changed on its own aggregate status field instead of the individual run. Xray updates that field as runs execute, which gets you close to what you're after without needing the run-level event.