Azure DevOps (ADO) fields that contain more than 32767 characters will be partially synchronized with Jira, meaning some content will be truncated. Updates from Jira will be not synchronized back to ADO once the character limit is reached.
Why?
Jira Cloud limits the number of characters that can be put into the fields like description, comments and custom fields of a rich text type. The limit is 32767 characters. Azure allows text fields to contain more characters.
In order to enable the synchronization, the synchronizer will automatically truncate text that exceeds the Jira limit. We'll show a message that the content of the field has been truncated and a link to the work item where the user can see the full text. See the examples below.
Fields containing truncated message won't be synchronized back to Azure
As long as the synchronized text field contains this text, it will not be synchronized back to Azure. We do this to prevent the overwrite of Azure field with the truncated text. If you want to resume the synchronization of such fields please remove the mentioned "You have reached the max character limit, the full text with ..." or "Field has reached Jira’s allowed max character limit of 32767. Exceeding content was truncated..." excerpt.
Truncated comments
Behaviour described above do not impact comments. Similar to fields those are also truncated to keep keep synchronization running. We do not support synchronizations of updates on already synced comments. Removing mentioned excerpts from synced comments will not have any impact.