> 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/product-updates-for-public-and-private-clouds-customers/release-notes/2024/24.71.0-public-and-private-clouds.md).
# 24.71.0 - public and private clouds
Discover updates in release 24.71.0 for public and private clouds: AI Vision and Jira sync enhancements, integration improvements, plus key defect fixes for optimal performance.
*Version 24.71*
*Includes all changes since version 24.63*
**New requirements and improvements:**
RQ059581 - AI Vision | Create requirements based on the files + UI improvements
RQ059776 - Jira sync | Allow mapping of only selected values and ignore other field values for the sync
RQ059770 - Remove old landing page and add agents and other files to the 'Integrations' page.
RQ060078 - 10 seconds delay added for automation agents before calling GetTasks
**Fixed defects:**
DF059799 - Jira Sync | NULL value is not mapped during automatic mapping of new values
DF059884 - Support | Jira Sync Configurator closes after adding a new field
DF060028 - Integrations | Additional wrong field is shown on the ‘Jira connect’ model
---
# 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/product-updates-for-public-and-private-clouds-customers/release-notes/2024/24.71.0-public-and-private-clouds.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.