Details
-
Bug
-
Status: Open
-
Blocker
-
Resolution: Unresolved
-
Xray DC 8.2.2, Xray DC 8.2.3
-
None
-
None
-
Environment
- Any Jira version
Description
Description:
When using automation with the “Field value changed” trigger, changes to Xray “test association” fields are not consistently detected. In particular, removing a Test from a Test Execution does not trigger the rule, and in our case, the trigger is unreliable across multiple Xray association fields.
Automation trigger: Field value changed
Fields affected (as shown in screenshot):
- Tests association with a Test Execution
- Test Sets association with a Test
- Test Type
- Tests associated with a Test Plan
- Tests association with a Pre-Condition
- Tests association with a Test Set
- Test Count
Pre-conditions
Create an automation rule as illustrated below
Steps to reproduce
- Go to Project settings → Automation and create a rule.
- Choose trigger Field value changed.
- Add one or more of the Xray association fields listed above (e.g., Tests association with a Test Execution).
- Add any simple action (e.g., Edit issue, Add comment, or create a new issue) so it’s obvious when the rule fires.
- Open an existing Test Execution.
- Add a Test to the execution.
- Remove a Test from the execution.
Expected result
The automation rule should trigger both when Tests are added and when Tests are removed, and should work consistently for all the listed Xray association fields.
Actual result
- The automation rule does not trigger reliably when a Test is added to or removed from a Test Execution.
- Additionally, the trigger is not reliable for the other listed Xray association fields (per screenshot), where changes are not detected consistently.