Problem Description

When a user who is logged in as a customer calls the create attachment public API endpoint and uses attachment wiki markup in the body property of the additionalComment object, the attachment wiki markup will be escaped.
See an example of this behaviour, where the attachment wiki markup is escaped in the response object:

Suggested Resolution

Allows customers to make comments using attachment wiki markup.

Why is this important?

The behaviour of escaping customers’ attachment wiki markup prevents customers from including attachments inline in their comment.
An example of a use case is transforming email content into Jira comments. It is important that the created comment accurately reflects the content of the original email. This behaviour of escaping the wiki markup prevents the comment from reflecting the original content. (see https://getsupport.atlassian.com/browse/JST-825693)

Workaround (if any)

Workaround 1.
When logged in as a customer, if attachment wiki markup is not used in the body property of the additionalComment object, then the image will be appended to the end of the comment. See:

This workaround is not sufficient if the use case of the endpoint requires inline comments.

Workaround 2.
When logged in as an agent, the attachment wiki markup will not be escaped.

This workaround does not work if it is not possible to make the comment as an agent