[Campaign or Iteration report] The generated DOCX file corrupted when a issue status contains a special character

Affected version : 12.RELEASE, 13.0.4.RELEASE, 14.0.0.RELEASE

When generating an iteration report or a campaign report in DOCX format, if the user checks the "Include (known) defect details" option, the generated document becomes corrupted and unreadable whenever at least one of the included defects has a status containing a special character (e.g., &).
Technical assumption: the status label is not properly escaped when injected into the DOCX internal XML structure, causing the document to become invalid.

Steps to reproduce

  • A Squash TM project configured with a Jira project for defect declaration
  • In Jira, at least one status containing a special character, e.g., Qualification & chiffrage
  • In Jira, set at least one defect (bug) to the status Qualification & chiffrage (or any other status containing an XML-sensitive character such as &).
  • In Squash TM, link this defect to a test execution so that it appears in the known defects of the iteration and campaign.
  • From the Management workspace, generate an iteration report or a campaign report and check the "Include (known) defect details" option.
  • Download the generated .docx file.
  • Attempt to open the file in Word, LibreOffice, or OnlyOffice.

Observed behaviour

The .docx file downloads successfully but cannot be opened — the document is unreadable/corrupted.

Expected result

The DOCX report opens correctly and the "defect details" section is properly generated regardless of the Jira status label, with special characters correctly escaped.

Edited by Elise Lebouvier