# Special compatibility for aqua and Jira fields
Starting from version 24.88 Jira sync configurator supports special compatibility of the fields
| Jira field, type | aqua, type |
| --------------------------------------------- | ----------------------------- |
| User field | Dictionary (single selection) |
| Labels | String |
| Linked issue, issue (default, interconnected) | String |
| Select list (Single choice) | String |
| Freeform | String |
| URL | String |
### Jira user field with aqua single select field
**aqua project template**
To set up the sync, first create a single select list (dictionary) field on the aqua project template.
You don’t need to create any values in aqua up front, as they will be populated automatically during the sync on a regular basis.
**Jira sync configurator**
In the Jira sync configurator, select the Jira user field and map it to a pre-created field in ITMS (aqua).
In the next screen of configuring value mapping, you can skip this step if you want to populate a field in aqua with all Jira users. The Jira sync will automatically fill the field with all Jira users and periodically (\~ 1-5 minutes) check for any new users, adding them to the aqua field.
{% hint style="info" %}
**Tip**: In case you want to check all available users in Jira, you can load the list by clicking on the corresponding button. The list will be populated in the ‘Jira users’ box.
{% endhint %}
To control which users are added as values in aqua, you can enable filtering by selecting 'Enable Filter.' In the box that appears, enter specific usernames or use a query to filter users based on specific criteria for syncing with aqua. For example, you might use a query to include only users whose names contain 'ch.'
Then users only matching this criteria will be always added to the list as values.
{% hint style="info" %}
Please note that Jira Server and Jira cloud handle queries and filtering differently. In Jira Cloud, you can specify exact usernames to be filtered. In Jira Server, however, you'll need to use a broader query to filter users, such as selecting all users whose names start with 'J'.
{% endhint %}
With this update, you no longer need to create users in aqua to replicate Jira users and ensure the sync works seamlessly. You can bypass aqua's default 'Assigned to' or 'Reporter' fields and instead add them as custom fields.
### Jira's linked issue, Issue and aqua's string field
**aqua project template**
To set up the sync, first create a string field in the aqua project template and name it according to your project requirements.
**Jira sync configurator**
In the Jira sync configurator, select the Jira linked issues field and corresponding pre-created string field in aqua and map them.
There are no additional steps needed from your side. Now you can link Jira issues to the Jira ticket and they will be referenced as IDs in aqua tickets.
At the same time you can provide IDs on aqua's side and those tickets will be linked on Jira side.
### **Jira's single select field and aqua's string field**
**aqua's project template**
To set up the sync, first create a string field on the aqua project template and give it the name that matches your project requirements.
**Jira sync configurator**
In the Jira sync configurator, select the Jira custom dropdown field and corresponding pre-created string field in aqua to map the fields.
At the next step, you can skip setting a default value if it’s not required. But in case you have this field as dependent on the other Jira fields or the values in this field may change dynamically, you can set the default value that will be set automatically every time a ticket is created in aqua.
Simply select from the dropdown the value from Jira and it will be added to the sync.
### Jira's freeform field and aqua's string field
**aqua project template**
To set up the sync, first create a string field on the aqua project template and give it the name that matches your project requirements.
**Jira sync configurator**
In the Jira sync configurator, select the Jira freeform custom field and corresponding pre-created string field in aqua for mapping.
There are no additional actions needed from your side, so just save the sync.
Once you add any text to the string field on the aqua side, it will show in the corresponding box field on Jira side and vice versa.
### Jira labels and aqua string field
**aqua project template**
To set up the sync with Jira labels, first create a string field on the aqua project template and give it the name that matches your project requirements.
**Jira sync configurator**
In the Jira sync configurator, select the Jira label field and corresponding pre-created string field ‘Label’ in aqua for mapping.
There are no additional actions needed from your side, so just save the sync.
Once you add any text to the Label field on aqua, it will create a label on the Jira side.
If you remove or add new labels, this change will be reflected in the aqua tickets.
If you want to add multiple labels in aqua, just add as many as you need separating them with comma or semicolon.
### Jira URL and aqua string field
**aqua project template**
To set up the sync with Jira URL field, first create a string field on the aqua project template and give it the name that matches your project requirements.
**Jira sync configurator**
In the Jira sync configurator, select the URL custom field and corresponding pre-created string field in aqua for mapping.
No additional steps are required from your side. From now on if you provide a link in aqua it will be added as a link on the Jira project.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.aqua-cloud.io/documentation/integrations/jira-sync-synchronize-items-between-aqua-and-jira-projects/fields-mapping/special-compatibility-for-aqua-and-jira-fields.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
