> 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.md). # Jira sync: synchronize items between aqua and Jira projects Biderectional syncronisation of Jira issues and aqua tickets Efficient project management often requires integrating tools to ensure smooth communication and collaboration across teams. aqua’s Jira sync tool is designed to bridge the gap between these two platforms, enabling a seamless bidirectional synchronization of defects and requirements from aqua to issues in Jira. ### Key Features of the aqua-Jira Sync **Bidirectional Synchronization**\ aqua and Jira sync effortlessly, ensuring updates to defects or requirements in one system reflect accurately in the other. This allows teams to work in their preferred platform without missing any critical updates. **Fields and values sync**\ Keep all relevant information aligned by syncing fields and their values between the two systems. Changes to key fields, such as priority, status, or custom fields, are automatically reflected in real time. **User mapping**\ aqua's Jira sync supports user mapping, ensuring actions and updates are correctly attributed to the corresponding team members in both tools. This minimizes confusion and maintains accountability. **Ticket content synchronization**\ Every detail matters. The sync ensures that ticket descriptions, comments, and other content are preserved and consistently updated across aqua and Jira. **Attachment handling**\ Attachments are integral to defect and requirement management. aqua’s sync supports the bidirectional transfer of attachments, making sure no context is lost during collaboration. --- # 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.md?ask=&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.