> 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/synchronisaton-of-subtasks-with-aqua.md).
# Synchronisaton of subtasks with aqua
Synchronize Jira subtasks effortlessly with aqua projects. Learn how to enable, map, and keep subtasks in sync for seamless cross-platform collaboration.
### What needs to prepared?
1. If you're already synchronising Jira's items with the Requirements and or you would like to separate your Subtask in your aqua's element repository please create a new folder in aqua where you will store all your subtasks:
2. Move to the project configuration template and add separate ID field (e.g. Parent ID):
{% hint style="info" %}
Make sure that you have activated the field with double click - by clicking on the red dot next to this new field
{% endhint %}
### Setting up the synchronisation:
1. Follow the same steps as in the video [First synchronisation setup](https://docs.aqua-cloud.io/documentation/integrations/jira-sync-synchronize-items-between-aqua-and-jira-projects/first-synchronisation-setup):
2. After you entered the server name, provided the jira user with Api Token the configuration should be read successfully. - for the data center it's your Jira's credentials not API token
3. Next step is to adjust the path and choose the correct item type:
6. After it's done, you need to adjust the Parent ID field that you created previously:
7. Then you can continue with mapping the fields and enjoy your subtask synchronisation.
{% hint style="info" %}
Make sure you name your synchronisation in a way that will help you easily locate this later:
{% 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/synchronisaton-of-subtasks-with-aqua.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.
.png?alt=media&token=3b89cf9f-192a-4fd3-bae0-d85692052794)
