25.123.0 - public and private cloud
π€ AI-Powered Defect Creation
Creating defects just got a whole lot easier. You can now use AI Copilot to generate detailed, professional defect reports in seconds - no more manual writing or formatting.
Here's how it works: When you're running a test and mark a step as "Failed" or "Blocked," a new "Create with AI" button appears. Click it, and the AI instantly generates a complete defect report with background information, reproduction steps, actual results, and expected results.
You can also create AI-powered defects directly from the navigation page or defect page. Simply describe the issue by typing, using voice narration, or uploading a file (screenshots, PDFs, Excel files, and more). The AI analyzes your input and creates a structured defect report that you can refine with additional instructions before saving.
This means faster bug reporting, more consistency across your projects, and less time spent on documentation. Whether you're in the middle of a test execution or documenting an issue you discovered elsewhere, AI Copilot has you covered.
π Multilingual AI Copilot
AI Copilot now speaks your language. System administrators can configure a default output language in settings, choosing from English, German, French, Spanish, Italian, Polish, Portuguese, or Hindi.
Once set, all AI-generated content - from chat responses to requirements, test cases, and test data - will be produced in your selected language, regardless of what language you use for input. This makes AI Copilot more accessible for international teams and ensures consistency across all generated content.
β οΈ Important: π§ Email Notification Defaults Have Changed
We've redesigned how item change notifications work to give you better control and reduce unnecessary emails. Here's what's changed and what you need to know:
What's Different: Email notifications for item changes are now disabled by default for new projects. This means when you create a new project, you won't receive email notifications about item updates like status change, until you choose to enable them. Your existing notification settings remain unchanged - if you already have item change notifications configured, they'll continue working exactly as before.
Why This Matters: Previously, many users received hundreds of unnecessary emails about item modifications, especially from technical sync accounts or automated processes. By starting with item change notifications off, you can now intentionally select only the item updates that matter to you, keeping your inbox clean and focused.
What You Should Do:
If you create a new project, remember to configure item change notification settings in your project default notifications configuration to enable the updates you want to receive.
Review your project default notification settings to ensure you're getting the information you need about item changes
Another step to optimize the amount of emails is reached: we solved the issue where the setting "Do not notify me if I made the change" was not always functioning correctly. Now you can keep your inbox clean and focused.
β‘ Streamlined Test Execution
Another improvement for testing workflows: a new project setting lets you enable auto-advance to the next step when marking steps as Failed or Blocked, eliminating unnecessary pauses and extra clicks during test runs.
We've also fixed an issue where Essential license users couldn't manually execute automated test cases - they now have full access to manual execution options.
β
Mandatory Descriptions for Quality Control
Project administrators can now make the description field mandatory for any item type at the project level.
When enabled, you'll see clear indicators that descriptions are required, and the system won't let you save items without them, ensuring consistency and preventing integration issues.
π Jira Sync: Eliminating Timing Problems
We've improved how aqua handles integrations to make your workflow smoother.
With βAutomatically create all new values from Jiraβ option enabled, the Jira sync now updates field values immediately during each sync rather than waiting up to 5 minutes, eliminating errors when new priorities or fix versions are added. This directly addresses sync issues that occurred when users created or updated items immediately after adding new Jira values.
For full list of changes, please see the Release Notes
Last updated
Was this helpful?