Xporter Bulk Test Plan export fails when getTestsStatus() exceeds Xray Cloud's 25 GraphQL operations limit

Description

When performing a bulk export of Test Plans via Xporter via the Issue Navigator, the export fails if the filter's result set is large. The internal GraphQL request generated by getTestsStatus(){} exceeds Xray Cloud's maximum limit of 25 GraphQL operations per query. This limit is not defensively enforced before building the query, so testStatusQuery(){} can receive 26 or more Test Plan IDs, generating a query with 26+ GraphQL aliases. Xray rejects the request with:

HTTP 400: "The query exceeds the maximum number of operations of 25. Actual number of operations 26."

This exception propagates through the Lambda export flow and is converted into a generic export failure "An error occurred while exporting your issues.", which hides the actual Xray API error. 

Pre-conditions

• Xray Cloud and Xporter Cloud installed on the instance.
• A saved JQL filter returning a large set of Test Plans (Tested with a total ~3,000 tests across 60 test plans)
• An Xporter template that includes Test Plan/Test status mappings.

How to reproduce

1. Create or use a JQL filter returning a large number of Test Plans
2. Open the filter in the Issue Navigator.
3. Trigger a bulk export via Xporter with a Test Plan list template.
4. Observe the export progress stuck at 5% before throwing an error.

Actual result/Attachments

The export is accepted, progress jumps to 5% within a second, stalls at 5% then aborts with the generic error "An error occurred while exporting your issues."

Expected result

The export completes for large result sets where the Test Plan IDs are batched so that no GraphQL query exceeds the 25-operation limit.

Additionally, when an Xray API error does occur, it should surface with meaningful detail rather than the generic failure message, and export progress should update during the data collection phase instead of remaining at 5%.

Workaround

• Split the export into smaller filters
• Export from the Xray Testing Board
• Use Xray's Document Generator
• Reduce template complexity by removing Test Execution/Test Run related fields from the template.