Known limitations
Avion's rich text editor supports many different formatting types and options, with powerful features from tables to code block syntax highlighting, and more!
However, unfortunately, not all of these formatting options are supported across the many platforms that Avion integrates with – these limitations typically arise as a result of all the different document formats and standards that these platforms use.
Listed below are known limitations of third-party services that we integrate with.
Text formatting that isn't supported within the Avion toolbar will not be preserved (e.g. text highlighting, font colours, subscript, superscript, checklists)
Azure DevOps
Jira Cloud
Jira Server
GitHub / ZenHub
Code language selection in code blocks is not preserved
Azure DevOps
Jira Cloud
Jira Server
Fix version descriptions do not support rich formatting
Jira Cloud
Jira Server
You cannot start a new line with a pipe |
character
Jira Cloud
Jira Server
Pipe characters |
inside tables may lead to unexpected results
Jira Cloud
Jira Server
Plaintext HTML (encoded or not) authored outside of Avion may not be interpreted as expected. This is due to inconsistencies in the data we receive
Jira Cloud
Jira Server
Tables, images and lists are not preserved within blockquotes
Jira Cloud
Inline images that are inserted outside of Avion may not be displayed. This is a permissions issue that cannot be worked around
Jira Server
Code blocks contain an additional line break
Jira Server
Images that were inserted outside of the Avion editor occasionally fail to show. Resolved by consistently using the correct project URL (https://go.avion.io/ado-urls)
Azure DevOps
Tables look terrible compared with Avion. Unfortunately, this is out of our control!
Azure DevOps
Tables are not supported
Trello
Sibling blockquotes will always be merged
Trello
Escaped special characters authored outside of Avion may behave unexpectedly in Avion — e.g. \'
or \&
Trello
GitHub / ZenHub
Last updated