> 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.114.0-public-and-private-clouds.md).

# 24.114.0 - public and private clouds

Discover bug fixes in version 24.114.0 for public and private clouds, including Jira sync photo retention, filter visibility, test case execution, role management, and navigation.

*Version  24.114*

*Includes all bug fixes since version 24.108*

<mark style="color:red;">**Fixed defects:**</mark>

* DF060497 - Jira sync | Photos are lost during Jira synchronization
* DF060656 - Filters | Applied filters are not visible in views and charts when savedoption was used in a previous generation until page reload
* DF060725 - Test case | If the field "Tested version" is not enabeld, then it is not possible to run automated testcase
* DF060618 - User administration | Expand/collapse doesn't work on the roles and permissions table
* DF060570 - Navigation | Not possible to remove some applied filters


---

# 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.114.0-public-and-private-clouds.md?ask=<question>&goal=<user_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.