Test Repository Path doesn't export the full Path

Description
${TestRepositoryPath} stops resolving to the actual Test Repository folder path when used inside a Document Generator template that iterates Test Runs on a Test Execution. Instead of the path, the field renders as blank or as the literal string "Test Repository". No changes were made to the affected template; the field previously resolved correctly and stopped working within the last month.

Pre-conditions

• Xray Cloud project with Document Generator enabled.
• Tests organized into Test Repository folders (not sitting at root).
• A custom Document Generator template that loops over Test Runs within a Test Execution using # {for testruns}, and references ${TestRuns[n].TestRepositoryPath} for each row.

How to reproduce

1. Create a Test Execution containing Test Runs whose Tests live in a non-root Test Repository folder (ideally nested, e.g. Test Repository / FolderA / FolderB).
2. Build or reuse a Document Generator template that iterates Test Runs #{for testruns} and prints ${TestRuns[n].TestRepositoryPath} for each row.
3. Open the Test Execution issue, click the "..." menu → Xray - Document Generator, select the template, and export (XLSX or DOCX).
4. Open the exported file and check the Test Repository Path column/field.

Actual result/Attachments
The Test Repository Path field is blank, or shows the literal text "Test Repository" for every row, regardless of the Test's actual folder.

Expected result
Each row shows the full folder path of the Test Repository folder containing that Test Run's Test (e.g. "Test Repository/FolderA/FolderB"), matching prior behavior.

Version

• Xray Cloud