Summary

Currently, on Jira Align, the Rich Text synced from Jira to Jira Align, is handled by the Parameter Text formatting type, and according to the Jira Align Manual, the options and its description are:

Jira text formatting type. elect how information in description and acceptance criteria fields should be formatted. The connector automatically detects which tool is being connected to and the editor being used in Jira to intelligently select this setting value. This will determine the editor functions available in these fields:

• None (plain text) synchronizes the text as-is.
  Note: Jira Align environments will sync wiki markup feature descriptions for features in programs synced with Jira, even if this setting is set to None.

• HTML maintains rich text content in Jira and Jira Align. We recommend selecting this value if you’re connecting to a Jira instance using a third-party editor that saves in HTML like JEditor.

• Jira rendered field saves feature and story description and acceptance criteria field information as wiki markup. For feature descriptions, this is a bi-directional sync.

• • For story descriptions, as well as feature and story acceptance criteria, the rich text sync is a one-way pull from Jira into Jira Align and data is read-only. To view story description pulled details, select the eye icon next to the story description. Task and defect description information will be synchronized as plain text. We recommend selecting this value if you’re connecting to Jira Cloud or Jira Data Center.

Enhancement

It would be really beneficial to the users if Jira Align could render the rich text directly in the Description field in all cases when syncing it from Jira (DC or Cloud), avoiding the step of clicking on the Eye Icon, as happens with Jira Rendered.