> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/integrations/jira-sync-synchronize-items-between-aqua-and-jira-projects/formatting-support.md).

# Formatting support

Seamlessly sync headers, lists, tables, images, and more between aqua and Jira projects - preserving rich formatting for requirements and defects. Learn about new support and current sync limits.

Starting with version 25.30, we've significantly improved formatting synchronization between aqua and Jira, enhancing clarity and consistency for your requirements and defects management.

Now, when syncing data between aqua and Jira—whether from aqua to Jira or Jira to aqua—the following formatting elements are fully supported:

* Headers
* Bold text
* Italicized text
* Text colors
* Tables
* Ordered (numbered) and unordered (bulleted) lists
* Code snippets
* Embedded images
* Videos (coming soon)

This enhanced support applies in both directions, ensuring that your important content retains its intended formatting regardless of the platform.

{% hint style="warning" %}

### ⚠️ CURRENT  LIMITATIONS

{% endhint %}

However, please note that some specific formatting options  and speicifics available in Jira are not yet supported in synchronization:

#### **Dashed (---) dividers. Syncing from Jira to aqua**

{% tabs %}
{% tab title="in Jira" %}

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2Fr1j8lfMPhJNWTjygIhLE%2Fimage.png?alt=media&amp;token=8456601f-c18e-4256-9b70-7628f5d0da1d" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="in aqua" %}

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FtD6m9SS3OOQYBirngn9l%2Fimage.png?alt=media&amp;token=4fe9b0e1-59ab-473e-87fc-b59a2d16c4bc" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**What will happen during the bi-directional sync:**

If a user updates the aqua ticket after the initial sync, the divider in the corresponding Jira issue will be removed upon resync
{% endhint %}

#### Image alignment (e.g., left, right). **Syncing from Jira to aqua**

{% tabs %}
{% tab title="in Jira" %}

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F327Zc3Q3AlrRWhZyoYvb%2Fimage.png?alt=media&amp;token=6329e456-92fd-4262-8f77-c18c0517b6ca" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="in aqua" %}

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FNRIZsV9rGE3NxNMGxnXS%2Fimage.png?alt=media&amp;token=97e00b46-f107-4e86-9d86-8603904adbb0" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**What will happen during the bi-directional sync:**

If a user updates the aqua ticket after the initial sync, the image in the corresponding Jira issue will be placed on the right between the content
{% endhint %}

#### Exact image sizes or resizing them according to Jira specifics

Jira has a special logic on the image reszing upon adding it to the work item, and additional logic on receiving the images upon syncing back to Jira.

When adding a big image to an aqua ticket, upon sync Jira resizes it to a small preview.

{% tabs %}
{% tab title="aqua" %}

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FC9otSXK9B7L12zQNUTIz%2Fimage.png?alt=media&amp;token=324b5daf-ed74-4edf-9936-ae842217ee0a" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Jira" %}

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F3NtJfYFeZztpxJajtcis%2Fimage.png?alt=media&amp;token=368fead6-8c2b-4790-b995-da23a2e31587" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**What will happen during the bi-directional sync:**

If a user updates the Jira ticket without resizing the image, the synced image in the corresponding aqua ticket will also appear in a smaller size.\
✅ *To avoid this, please resize the image to the desired dimensions in Jira before saving and syncing it back to aqua.*
{% endhint %}

#### Jira-specific special blocks

Currently, aqua does not support embedded Jira-specific blocks. As a result, syncing work items that contain these blocks may lead to formatting issues or broken content in aqua.

We’re actively exploring ways to support the most commonly used block types in future updates.\
📩 *If there are specific blocks you frequently use, please let us know, we’ll evaluate the possibility of adding support for them in aqua.*

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FqHdouhBYrejf09GcZtiA%2Fimage.png?alt=media&amp;token=b42a4131-7837-4fec-bbe2-707dc4e03ce6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

#### Jira Cloud vs Jira Data Center

While the formatting synchronization works for both Jira Cloud and Jira Data Center, slight differences might occur due to variations in how data is handled across these platforms.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aqua-cloud.io/documentation/integrations/jira-sync-synchronize-items-between-aqua-and-jira-projects/formatting-support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.