25.123.0 - On Premise

⚠️ 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:

1

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.

2

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.

This is especially valuable if you sync with Jira or Azure DevOps, where missing descriptions can cause sync errors.

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