Xray Cloud app is not eligible for data residency migration due to missing inScopeEUD definition

Description

The latest version of Xray - Test Management for Jira Cloud introduced egress permissions to additional URLs, including amazonaws.com. However, the inScopeEUD property was not added/defined in the app manifest.

As a result, Xray is displayed as "Not eligible" for app data residency migration in the Atlassian Admin Hub.

Atlassian has confirmed that their internal APIs have been updated and the customer's scope placement is correctly reflected as EU. However, the app will continue to appear as ineligible until the missing inScopeEUD property is added/defined in the Xray app manifest.

Pre-conditions

• Xray Cloud is installed on a Jira Cloud instance.
• The customer is eligible for app data residency migration.
• The latest Xray Cloud version is installed.

How to reproduce

1. Navigate to the Jira Cloud Administration / Atlassian Admin Hub.
2. Open the app data residency settings.
3. Locate Xray - Test Management for Jira.
4. Check the data residency migration eligibility status.

Actual result/Attachments

Xray is displayed as "Not eligible" for an app data residency migration.

Atlassian reported that this is caused by the missing inScopeEUD property in the Xray app manifest after new egress permissions were introduced.

Expected result

Xray should be correctly identified as eligible for app data residency migration when the customer meets the applicable requirements.

The Xray app manifest should define the required inScopeEUD property so that Atlassian can correctly determine the app's data residency eligibility.

Version

• Xray Cloud: Latest version/release at the time of reporting
• Jira Cloud: N/A

Workaround

No workaround is currently available.