Defect Traceability Report shows blank page due to CORS error after DC-to-Cloud migration (hostBaseUrl mismatch in fetchUserSettings)

Description

After migrating from Jira DC to Jira Cloud, the Defect Traceability Report renders a blank page for all users. The report's front-end code constructs an absolute URL using the legacy DC base URL (hostBaseUrl) when calling fetchUserSettings, causing the XHR request to be blocked by CORS policy. All other Xray reports are unaffected.

Pre-conditions

• Xray for Jira Cloud, instance migrated from Jira DC to Cloud.

• Client key registered in Xray still reflects the old DC URL, not the new Cloud URL.

• Defect mapping configured in Project Settings and defects are present in the project.

• Reproducible for all users on the instance.

How to reproduce

1. On a Jira Cloud instance that was migrated from DC (where the Jira base URL changed), open Xray and navigate to Reports > Defect Traceability Report.

1. Select a project and click Generate Report.

1. Observe the browser console for CORS errors.

Actual result/Attachments

The fetchUserSettings call (defect-traceability-report-action.js, line ~149) uses an absolute hostBaseUrl, targeting the old DC URL instead of a relative path. The POST request to generate the report is never triggered.

Expected result

The Defect Traceability Report should load and display data correctly after a DC-to-Cloud migration, in the same way all other Xray reports do. The fetchUserSettings request should use a relative URL (same-origin) so no CORS issue can occur.