Multiple spaces in Jira Paragraph field are collapsed to a single space in Xporter PDF export

Description

When exporting a Jira issue using the Xporter Cloud plugin, multiple consecutive spaces entered in the Description field are collapsed to a single space in the exported document when the field is rendered using the ${wiki:Description} mapping. The same field exported using ${Description} (plain mapping) preserves the spaces correctly, which indicates the issue is specific to the wiki rendering path. The issue reproduces in both PDF and DOCX exports.

Pre-conditions

• Jira Cloud instance with Xporter Cloud installed.
• A Jira issue with content in the Description field.
• An Xporter template that references the Description field using ${wiki:Description}.

How to reproduce

1. Open a Jira issue and edit the Description field.
2. Enter the following content exactly (six spaces between the code and the text):

   • Test
     123-09876      Sample Document

1. Save the issue.
2. Export the issue using an Xporter template that references the field as ${wiki:Description}, once to PDF and once to DOCX.
3. Open the exported files and inspect the rendered content of the Description.

Actual result/Attachments

In both the PDF and DOCX outputs, the six spaces between 123-09876 and Sample Document are collapsed to a single space:

Test
123-09876 Sample Document 

Expected result

Consecutive spaces entered in the Description field should be preserved in the exported document, matching exactly what was entered in Jira:

Test
123-09876      Sample Document 

This is the behavior observed when the same field is mapped using ${Description} (without the wiki: prefix), which confirms the source data is stored correctly and the issue lies in the wiki rendering path. The behavior is consistent across both PDF and DOCX export formats.

Version

• Xporter Cloud: Version 5.0.0
• Affected export formats: PDF and DOCX

Workaround

Use ${Description} instead of ${wiki:Description} in the template. This preserves whitespace, but the trade-off is the loss of rich-text formatting (bold, italics, lists, links, etc.) that the wiki mapping would otherwise render. Acceptable only when the Description contains plain text or when formatting is not required.