Details
-
Bug
-
Status: Waiting Approval
-
Medium
-
Resolution: Unresolved
-
Xray Cloud 6.13.0
-
None
-
None
-
Xray Cloud
Description
When exporting Tests, Test Runs, or Test Executions via Xray's Document Generator on Xray Cloud, the Assignee field is exported empty even though the issue has an active, correctly-permissioned user assigned.
- Pre-conditions
Xray Cloud (Document Generator)
Test / Test Run / Test Execution assigned to an active Jira user
Exporting user has Jira admin access and the "Browse users and groups" global permission (confirmed present, both space and global)
- How to reproduce
Assign an active Jira user to a Test, Test Run, or Test Execution (tested with different active users, including the exporting user themself)
Run a Document Generator export using a template that includes the Assignee field (customer used "Xray Test Plan Basic with Cover Page Cloud_new_1 (4).docx")
Open the generated document/raw export and check the Assignee field
- Actual result/Attachments
The Assignee field is empty in the export, including in the raw export (assignee ID itself is blank). This happens consistently across multiple active users and multiple export attempts. Issues with no assignee correctly show "Unassigned," so the export pipeline itself is running and only the assignee value is being lost. Direct Jira REST calls made as the exporting user - both `/rest/api/2/search/jql?jql=key=<KEY>&fields=assignee` and `/rest/api/2/issue/<KEY>?fields=assignee` - correctly return the populated assignee (displayName, accountId, active: true), confirming Jira itself hands back the correct data and permissions are not the cause. HAR file (keyXL5-11455 (1).har) and console.txt were captured during a customer call and are attached to https://sembi.atlassian.net/browse/L3S-2344#icft=L3S-2344/SUPPORT-118501; screenshots of the empty export were also shared during that call.
- Expected result
The Assignee field should be populated with the assigned user's name in the export, consistent with how the "Unassigned" case is correctly handled today.
Attachments
Issue Links
- duplicates
-
XCC-3180 Loading...