DocGen Export in Cloud Exports Null/Blank for Unassigned Test Run Assignee Instead of "Unassigned" (missing parity with Server/DC)

Description
When exporting Test Run Assignee/Executed By using DocGen in Cloud, if a Test Run is Unassigned, the exported value is blank/null instead of displaying "Unassigned".

In Server/DC, the following fields correctly export the value "Unassigned" when the Test Run has no assignee:

${TestRuns[n].AssigneeId}
${TestRuns[n].Executed By} 

However, in Cloud, the same fields export an empty value, resulting in inconsistent behavior between Cloud and Server/DC. To maintain feature parity between Cloud and Server/DC, DocGen exports in Cloud should display "Unassigned" whenever the Test Run is unassigned.

Pre-conditions

• A Test Run exists with no assignee assigned.
• A DocGen template contains one or both of the following fields:

• ${TestRuns[n].AssigneeId}
  ${TestRuns[n].Executed By} 

  How to reproduce

• Create or identify a Test Run with no assignee.
• Create a DocGen template containing:
• ${TestRuns[n].AssigneeId}
  ${TestRuns[n].Executed By}  

• Generate/export the document using DocGen in Cloud.
• Review the exported output for the assignee-related fields.
  Actual result/Attachments{}
• The exported document displays a blank value/null for unassigned Test Runs.
• No "Unassigned" value is shown.
  Expected result
  When a Test Run is unassigned, the export should display:
   

       Assignee: Unassigned
       Executed By: Unassigned    

   
  This behavior should match the existing functionality in Server/DC and ensure parity across platforms.

Version

• Xray Cloud 16.0.0

Workaround

Use the following code:

#{if (%{'${TestExecutions[m].TestRuns[l].AssigneeId}'.equals('')})} 
Unassigned 
#{end}
#{if (%{!'${TestExecutions[m].TestRuns[l].AssigneeId}'.equals('')})} ${fullname:TestExecutions[m].TestRuns[l].AssigneeId} 
#{end}