As a user, I want to be able to access Jira custom fields within Test Run iteration blocks (#{for testruns}) using ${TestRuns[n].<fieldname>}.

Description

Currently, it is only possible to access Xray custom fields within Test Run iteration blocks in Xporter templates, while Jira custom fields are not accessible at this level, limiting the data that can be included in exported reports.

User friction

Users who rely on Jira custom fields as part of their test reporting are unable to include that data in their Xporter templates when iterating over test runs.

Steps to reproduce (right now) / Actual Result:

1. Create an Xporter template with a #{for testruns} iteration block.
2. Attempt to reference a Jira custom field using ${TestRuns[n].<fieldname>} inside that block.
3. Export using that template.
4. Observe that the Jira custom field does not render.

IMPACT

What would improve if solved:

Users would be able to build more complete reports by accessing any Jira custom field directly within #{for testruns} blocks, without needing additional workarounds.

Impact on stakeholders:

This can impact both the teams building Xporter templates, who are unable to include the required fields in their reports, and the stakeholders consuming those reports, who end up with incomplete test execution data.

Current workaround:

Users can recreate the needed Jira custom field as an Xray Test Run custom field.

CONTEXT & EXAMPLES: 

A user building a Test Execution report wants to display a Jira custom field alongside each test run using ${TestRuns[n].<fieldname>} inside a #{for testRuns} block. This is not possible currently as only Xray-native fields are supported at this level.

Workaround risk:

Workaround requires duplicating field maintenance across both Jira and Xray, and may not be feasible when there is existing data or historical values tied to the original Jira custom field that cannot be replicated.