Atlassian Connector Issue

When connected to Atlassian via API we are seeing it write in a string instead of the ADF format that Atlassian expects. Has anyone found a work around for this or is this something AWS needs to update on the connector?

Hi @dougsallas and welcome back to the Quick Community!

Couple quick questions - are you hitting this on Jira or Confluence, and which action (create issue, add comment, update page)? Also, are these connectors the native Quick connector or through a MCP server integration?

Asking because Atlassian’s v3 API doesn’t accept plain strings for rich text fields. It needs content in ADF (Atlassian Document Format), which is structured JSON. If the connector isn’t converting your text to ADF before sending it, Atlassian will either reject it or render it literally. Through some research this seems like a known pain point across Atlassian integrations and not something you can fix on your end.

A recent post had a similar issue and it got resolved through a support ticket. In this case I would do the same and recommend opening an AWS Support case.

Hey Jacob, I work with Doug. The connector uses v3 API. The connector isn’t converting to ADF before sending it, causing it to be treated literally by Jira.