> 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/product-updates/2025/25.61.0-public-and-private-cloud.md).

# 25.61.0 - public and private cloud

## 📹 **Jira sync now supports videos**

You can now sync videos between aqua and Jira.\
When a video is added to a Jira ticket or comment, the URL will automatically appear in the linked aqua item during sync. Users can preview the video directly in aqua if it’s in one of the supported formats:

{% hint style="info" %}

* .mp4, 
* .mov, 
* .webm, 
* .mkv, 
* .m4v,
* .3gp, 
* .asf, 
* .flv, 
* .mpeg, 
* .wmv, 
* .m2ts
  {% endhint %}

**Why this matters:** You can better understand reported issues, reproduce bugs faster, and improve collaboration between QA, developers, and stakeholders.

## **⌨️ API update: pass test execution status without steps**

For teams using external testing tools or automations, this update is can save a lot of time.

You can now set or update the overall status of a test execution — whether it’s a standalone test or part of a larger scenario — through the API, without needing to touch each individual step.

✅ Supported statuses: **Passed, Failed, Blocked, Not applicable, Not run**\
✅ Applies to single test runs and tests within scenarios\
✅ When setting the overall status, all steps will automatically inherit it

**Important:**

* If you attempt to set statuses like **Aborted, Queued, Waiting, or In Progress** on manual executions, you will receive a clear error message.
* Finalized executions can’t be updated and will return an `InvalidArgument` error.

## **🤖 AI Copilot: use JSON files for item generation**

AI Copilot just got more flexible!\
You can now upload a JSON file to automatically generate test data, requirements, or test cases. This gives you more control over structured input and helps speed up the creation of complex or repetitive items.

**As always, we love hearing your feedback. Let us know what you think or if you need help getting started!**


---

# 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/product-updates/2025/25.61.0-public-and-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.