Zephyr for JIRA: (spaces) in Fields causing error from XML view

Chad

We are using Zephyr for JIRA to help document test cases. Our test data is always changing as our database is refreashed and masked periodically, therefore we want to enter SQL into the Test Data field of a Zephyr Test Step. However, when viewing the issue as XML or as a feed in Confluence, the XML is invalid. Doesn't seem like Zephyr is appropriately scrubbing the spaces like other JIRA Fields.

For example, here is SQL that we like to put in the Test Data section of a Step...

SELECT
    a.column1
FROM
    tableA a
WHERE
    a.column1 > 5;

Where the indentions are spaces.

When viewing this issue in JIRA, no issue. However, when viewing the issue in XML format an error is displayed. Error states:

This page contains the following errors:

error on line 77 at column 7: Entity 'nbsp' not defined

Below is a rendering of the page up to the first error.

When you look at the source for the issue in XML format you see that the spaces are all represented (as  ), which apears to be the issue for valid XML.

...
<step>
  <orderId>2</orderId>
  <step>step with tabs</step>
  <data>SELECT<br/>
    a.column1<br/>
FROM<br/>
    tableA a<br/>
WHERE<br/>
    a.column1 > 5;<br/>
  </data>
  <result>Should work</result>
</step>	
...

When trying then to view this issue or a filter with this issue in Confluence, it fails since the XML appears to be invalid. This blocks the ability to feed issues, specifically for Confluence.

Options: Could Zephyr fields be JIRA wiki field an scrub spaces better? (might have other advantages than just a plain field.

Any input or help would be appreciated!

Thank you!

Chad

Upgraded to Zephyr for JIRA 1.7.3.1043 and issue is resolved.

<step>
	<orderId>1</orderId>
	<step><![CDATA[ step with spaces ]]></step>
	<data><![CDATA[ SELECT
    a.column1
FROM
    tableA a
WHERE
    a.column1 > 5;
 ]]></data>
	<result><![CDATA[ Should work ]]></result>
</step>	

Also, Zephyr for JIRA - Release Notes provide a high level description of the features/bugs resolved (not quite as "Open Company, No Bullshit" as Atlassian, but some insight).

Thank you to @Chirs Miller for your quick response and your team for providing a resolution!