Known limitations for HTML - Jira Wiki
The purpose of this document is to outline existing limitations in the conversion mechanism between Rich Text in Jira and HTML in Azure DevOps.
There are 3 main groups of known limiting factors of said conversion
Nonexistent styling in Jira - some styles possible in HTML are just not possible in Jira. Those limitations are not likely going away.
REST API limitations. - We use REST API to communicate both with Jira and Azure DevOps. Sometimes this means of communication is having fewer options than live editing. Those limitations might be fixed by changes in Jira and ADO REST API. We have little influence over it.
TFS4JIRA internal conversion limitations. The sheer amount of combinations of tags can create corner cases that are badly handled by our internal mechanism. This list is constantly being built and updated as we add new fixes.
As with any known limitation list, it’s never fully complete. If you happen to encounter any problem while synchronizing the HTML field to the Jira Rich text field that is not listed here, please do let us know here: Support portal
Nonexistent styling in Jira
Highlighting.
How it should be synchronized:
How it is synchronized:
REST API limitations
Formatting added to spaces or in the middle of a word.
How it should be synchronized:
How it is synchronized:
Reason: https://community.atlassian.com/t5/Jira-Core-Server-questions/How-do-I-bold-part-of-a-word-in-a-JIRA-field/qaq-p/24085
TFS4JIRA internal conversion limitations
Strikethrough
How it should be synchronized:
How it is synchronized:
Code Panel
How it should be synchronized:
How it is synchronized:
Mixing Bold and Italic and having Italic encapsulated in Bold.
How it should be synchronized:
How it is synchronized:
Mixing ordered and unordered list
How it should be synchronized:
How it is synchronized: