> 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-on-premise-customers/release-notes/2024/24.71.0-on-premise.md).
# 24.71.0 - On Premise
Discover what’s new in On-Premise 24.71 - Azure DevOps integration, Jira Data Center 9.12.10 support, improved sync, and key defect fixes for enhanced performance.
Version 24.71
Includes all changes since version 24.53
**New features and improvements:**
RQ058666 - Integration with Azure devops
RQ059356 - Dependencies | Automatically add dependency of the sub-requirements to a parent requirement
RQ059643 - Jira Plugin | Add compatibility with Jira Data Center Version 9.12.10
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
**Defects:**
DF059537 - Search bar | The dropdown icon is misaligned
DF059504 - Test execution details | Steps are not showing the proper information and the information from the first step is displayed
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-on-premise-customers/release-notes/2024/24.71.0-on-premise.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.