-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 10.131.3
-
Component/s: Epics - Action
-
8
-
Severity 2 - Major
-
No
Issue Summary
If the master toggle "Formatted Text" is enabled, when exporting Epic or by accessing the "Status Report", the Jira Align does not encode a few special characters, in the "Description" field.
Steps to Reproduce
- Enables the master toggle "Formatted Text"
- Go to any Epic on Jira Align
- Update the Description with special characters (such as &, ^, %) and with empty space at the end of each line.
- Save the Epic
- Go to "Status Report"
- Also, close the Epic and export it, unselecting the toggle "Include HTML formatting in the exported"
Expected Results
The Jira Align encodes the reserved HTML entities regarding the special characters.
Actual Results
Jira Align is not encoding the reserved HTML entities regarding the special characters when exporting the Epics and if accessing the "Status Report"
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JIRAALIGN-7413 REST API: Epic Description Field Includes HTML Tags
-
- Closed
-
-
JIRAALIGN-7166 Epic Description in Enterprise Insights having two separate columns: one to store rich-text formatting and one to store the unformatted values
- Gathering Interest
-
ACE-5520 Loading...
-
ALIGNSP-24161 Loading...
-
ALIGNSP-24192 Loading...
- relates to
-
JIRAALIGN-6898 Description in Epic Status Report int rendering rich text
-
- Closed
-
-
PS-167141 Loading...
- is connected to
-
JAWM-7074 Loading...
- mentioned in
-
Page Loading...
- resolves
-
ALIGNSP-25482 Loading...
-
PS-167045 Loading...
-
PS-167464 Loading...
-
PS-168983 Loading...