Exporting Cucumber Tests - REST returns 500 when an exported test is linked to an archived requirement

Description

/api/v2/export/cucumber returns 500 "Internal Application Error!" when an export pulls in a Cucumber test linked to an archived requirement and the global setting "Generate features by requirements" is on.

The exporter appears to attempt construction of the @REQ<key> tag for the linked requirement. The lookup fails on the archived issue, and the resulting exception is not handled and it surfaces to the caller as a generic 500 with no actionable detail._

Pre-conditions

• Xray Cloud
• Cucumber Settings → Generate features by requirements enabled
• A Cucumber test linked to a Requirement via the Xray "tests" link
• The linked requirement is archived in Jira
• A Test Execution containing that test

How to reproduce

1. Create a Cucumber test with any valid Gherkin scenario.
2. Link it to a Story via the Xray "tests" link.
3. Add the test to a Test Execution.
4. Enable "Generate features by requirements"
5. Archive the Story.
6. GET /api/v2/export/cucumber?keys=<TestExecutionKey> with a valid Bearer token.

Actual result/Attachments

HTTP/1.1 500 Internal Server Error
Content-Type: application/json; charset=utf-8
ETag: W/"27-cYRnXRR93cPrq7A4d4C00Ae3v7s"
Content-Length: 39

{"error":"Internal Application Error!"}

same internal failure path.

Expected result

The endpoint should either skip archived linked requirements during tag generation and return a successful 200 response, or return an appropriate 4xx status code that identifies the offending issue key in the response payload. In its current state, the API consumer has no means of determining which issue is causing the failure.

Version

• Xray Cloud, 10.0.1

Workaround

Unarchive the linked requirement, remove the "tests" link, or globally disable "Generate features by requirements".