Document Generator: JQL-based nested iterations (e.g. requirementTests()) not resolved, nested tables render empty

Xray Cloud Document Generator does not execute JQL-based nested iterations (e.g. custom functions like requirementTests()) during export. The top-level JQL runs fine, but nested tables driven by a JQL clause render completely empty, even though the same JQL returns valid results when run directly in the Jira Issue Navigator. The same template works correctly on Jira Data Center.

Pre-conditions

Project and Document Generator templates migrated from Jira Data Center to Jira Cloud, template syntax unchanged.

Xray custom JQL functions and DC-compatible JQL options enabled on the Cloud tenant.

Template contains a nested JQL-based iteration loop instead of a predefined Xray field relationship, e.g. issueType = Test AND key in requirementTests($key).

How to reproduce

Migrate a project and its Document Generator templates from Jira DC to Jira Cloud without altering template syntax.

Confirm Xray custom JQL functions and DC-compatible JQL options are active on the Cloud tenant.

Use a template with a nested JQL iteration loop, e.g. issueType = Test AND key in requirementTests($key).

Open a requirement issue in Jira Cloud, go to the Xray Document Generator, select the migrated template, and trigger export.

Actual result/Attachments

The Document Generator successfully executes the nested JQL query iteration, retrieves all linked test cases associated with the requirement, and fully populates the table with test details (including Test ID, summary, execution result, and test steps), identical to the successful output produced in the Jira Data Center environment.

Confirmed via a stripped-down isolated template ( redacted.docx ) and by hardcoding the $key variable - table still empty either way. Root cause (per dev analysis): getIterable() in field-mapper/index.ts only resolves predefined Xray field relationships (testTargetIssueIds, testPlanTargetIssueIds, subtasks, issue links); it never detects or executes JQL-based iterations, so the $key substitution and JQL execution are skipped entirely for nested loops.

Screenshots showing expected vs. actual output are attached to the ticket; a HAR file (redacted.har) capturing the export attempt was also provided by the customer. Original production template (redacted.docx ) could not be shared due to sensitive content.

Expected result

The document generates partially; top-level data (such as the requirement ID and summary) appears correctly, but the nested test case table remains completely empty. No error message is displayed in the UI during export, despite the underlying JQL query returning valid results when executed directly in the Jira Issue Navigator.