> 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/2023/23.107.0-public-und-private-clouds.md).
# 23.107.0 - Public und Private Clouds
Version 23.107
Beinhaltet alle Änderungen seit der Version 23.92
Neue Funktionen und Verbesserungen:
RQ057879 - AI Copilot | Option to create new document types based on narration or notes
RQ049165 - Jira | Improve current Jira integration + new look and feel of the settings page
RQ049150 - Jira Sync | oAuth for Jira
RQ049450 - Dashboards | Part 2 | Re-design the chart page
RQ049440 - UI/UX | Add option to create projects from the navigation and items from the project title place
Gelöste Fehler:
DF058149 - User is logged out when navigating from external site to aqua
DF058099 - Dashboard | Table chart | The view is broken when the table chart is bigger than a chart box
DF057875 - aqua | capture | When the template is applied, the information from capture is not added to RQ or DF
DF058097 - Dashboard Edit Chart popup opening with flickering effect
---
# 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/2023/23.107.0-public-und-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.