Epic Description in Enterprise Insights having two separate columns: one to store rich-text formatting and one to store the unformatted values.

After the following implementation of Epic Description fields with Rich Text in JA and EI:

• On March 1st Release Notes - Jira Align EI enhancements and features version 10.130.X which was released on March 1st.

  New content/suggestions

  • HTML tags used for rich-text formatting in Jira Align UI fields are removed from values in the following columns and views within the current_dw and export_dw schemas:
    • Epic Description in Epic and Epic History views
    • Capability Description in Capability and Capability History views
    • Hierarchy Description in Hierarchy view
    • Override Notes in Objective Score Override History view
    • Health Comment in Hierarchy Health History view

Before this, you would have everything in Epic Description as plain text in the UI and DB/EI.

• On March 29th Release Notes - Jira Align version 10.131.x

  Rich text editor on the description field for epics and capabilities

  In version 10.130, we announced rich text editing in the description field for epics and capabilities. This feature has now been turned on for everyone.

Customer is being impacted by this change and in order to support, what the customer is requesting we would need two separate columns: one to store rich-text formatting and one to store the unformatted values. This would need to be implemented within the Jira Align application and may have implications to performance as two columns would need to be updated.