...
Jira Cloud limits the number of characters that can be put into the 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 avoid the synchronization failures, the synchronizer will automatically truncate text that exceeds the Jira's 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 original text (from ADO). See the examples below.
...
As long as the synchronized text field contains this textwarning message, it will not be synchronized back to Azure. We do this to prevent the overwrite of Azure corresponding ADO field with the truncated text. If you want to resume the synchronization of such fields 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. Important: removal of the warning text will have no effect on Jira's comments. Comments are synchronized once, so their update doesn't result in another synchronization attempt.