Hi Alfred,

This is both a defect and "by design". Let me elaborate.  

Before 24.1, Rich Text fields were storing the HTML code in both PARAMETER and VISIBLE_PARAMETER columns. This caused some problem when trying to insert Rich Text field contents in Excel Reports/Exports, or in the Request List portlet (as it escapes HTML content by default for security reasons). 

As a result, in PPM 24.1, we modified Rich Text fields and now "extract" a rough text-only version of the HTML content to save it in the VISIBLE_PARAMETER column, which can now be safely used in Excel reports or Request List portlet. The HTML content remains in the PARAMETER column of the field. This part is "by design".

The "defect" part is that agile Field synchronization should use the PARAMETER value for rich text field instead of the "VISIBLE_PARAMETER" - and this is a bit of an ER, because when synching a PPM text field to an agile tool, it makes sense to synchronize the VISIBLE_PARAMETER field by default - so the current logic makes sense in a generic setting when handling text field - it just doesn't apply specifically to rich Text fields with the new 24.1+ logic. So we'll need to make some adjustment to the code and read from the PARAMETER column instead when synchronizing a Rich Text field. 
Note also that some other agile tools might not support the HTML syntaxt for their rich text fields (maybe they use Markdown syntax), and in that case it would make more sense to send them the "pure text" version of PPM Rich Text fields. But clearly that's not the case for Octane, and since we were sending the full HTML code before, I'd advise you to submit a Support ticket (pointing to this thread if needed) to get this issue addressed by reading from the PARAMETER column for Rich Text fields.

Thanks for bringing that to our attention!

Thanks Etienne, will submit support case.

Fixed in PPM 24.4 (October release) - and I think you already got a hotfix for your current version already.

Thanks for bringing that to our attention!

Thanks Etienne, we received the hotfix