> 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/additional-settings/allow-mapping-of-only-selected-values-and-ignore-other-field-values-for-the-sync.md).
# Allow mapping of only selected values and ignore other field values for the sync
Control which Jira field values sync with aqua by mapping only selected values, ensuring precise data transfer and filtering out irrelevant items.
Starting from the Jira sync 24.71 version, there is an option to map only needed values for the following fields:
* dropdown fields
* user fields (users not existing in one system)
* multichoice
It helps to keep the items synced between two systems, while only required field details are passed.
The option 'Ignore unknown values' could be added either to the whole sync or to individual fields.
By default, it's set on the global level.
If you want to set it for specific fields, simply remove the checkbox
The next to each dictionary or user fields, you'll see additional checkbox that you can enable/disable.
In cases, when 'Ignore unknown values' is enabled on the global or specific field level, then for then the setting 'Automatically create new values from Jira in aqua' is disabled.
---
# 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/additional-settings/allow-mapping-of-only-selected-values-and-ignore-other-field-values-for-the-sync.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.
