> 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/de-documentation/produktaktualisierungen-fur-kunden-von-public-und-private-clouds/release-notes/2025/25.103-public-und-private-cloud.md).

# 25.103 - Public und Private Cloud

Version 25.103.0\
Enthält neue Funktionen, Verbesserungen und Fehlerbehebungen seit Version 25.91.0

***

<mark style="color:green;">🆕</mark> <mark style="color:$success;">**Neue Anforderungen und Verbesserungen**</mark>

* **RQ067363** - Testrail | Allow to migrate from the on prem version of Testrail

<mark style="color:red;">🛠️</mark> <mark style="color:red;"></mark><mark style="color:red;">**Behobene Fehler**</mark>

* **DF067343** - Jira sync | Change 'bearer' to 'Bearer'
* **DF067894** - Jira sync | Failed to retrieve project configuration for team-managed board
* **DF067555** - Jira sync | Jira Data Center | Items don’t sync and there are no issues logged
* **DF066381** - Export | When exporting a test case, the condition is exported empty
* **DF067032** - Jira sync | Error when creating new issue while having priority mapped unidirectional
* **DF067098** - Items | Discussions | Deleted posts are included in the total number of posts
* **DF067081** - User administration | After the error message “Choose a different username” changes can’t be saved
* **DF067086** - User administration | User roles | Spelling error in the toast message

***


---

# 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/de-documentation/produktaktualisierungen-fur-kunden-von-public-und-private-clouds/release-notes/2025/25.103-public-und-private-cloud.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.