Allure TestOps 25.3.1 - 2025-07-16

New features

Custom fields

Updated the capabilities for configuring custom fields at both the Allure TestOps instance and project levels.

Single-select and multi-select fields

Added the ability to define the type of a custom field when creating it:

• Single-select custom fields allow users to select only one value from the list.
• Multi-select custom fields allow users to select multiple values from the list.

All previously created custom fields are considered multi-select by default. The type of existing custom fields cannot be changed.

Required fields

Updated the logic for required custom fields: at the Allure TestOps instance level, an administrator can now mark custom fields as required for the projects using that field. At the project level, the field can be marked as required by the project owner.

Global and project values

Added the ability to define global and project-level values for custom fields:

• Administrators can create global values that are automatically available in all projects where the field is used. Any of the values can be selected as the default.
• Project owners can create project-level values and set them as default. Additionally, administrators can promote one or more project-level values to global — this simplifies reusing values and speeds up field configuration.

Value locking

Added the ability to restrict custom field values at the project and Allure TestOps instance levels using the Lock values toggle. When enabled, users cannot add new custom field values and should choose values from the predefined list.

Value merging

Added the ability to merge custom field project values into existing or new values. Administrators can merge only into global values, while a project owner can merge into both global and project values.

AQL in test case filters

Added the ability to filter test cases using AQL queries. This feature is available under the "AQL in filters" feature flag.

• Integration with ClickUp as an issue tracker.

Added one-way integration with ClickUp which allows to connect Allure TestOps entities to issues in the ClickUp issue tracker.

Improvements

• Improved the export of test cases and launch results to PDF format. Reports now include:
  • attachments (screenshots, text, and tables) from test scenarios and their execution results;
  • icons showing the step execution statuses in test results.
• Improved the sidebar controls: it can now be resized, collapsed, or expanded using the cursor.
• Enabled the "Version history in test cases" feature flag by default for all users.
• Improved the defect search: added the ability to search by ID and description.
• Improved the issue tracker integration settings: when saving a new value in the Endpoint field, the system now suggests updating all issue tracker links.
• Optimized the database queries related to test results improving overall system performance.
• Updated logging for the IllegalStateException error related to invalid user sessions, it now returns a 401 status code.
• Added the display of user's first and last names:
  • in access settings;
  • when assigning a test in launches;
  • when selecting an assignee in test plans;
  • in comments on test cases and launches;
  • in widgets;
  • in project cards on the home page.
• Added the support for access token renewal rules when authenticating via an OpenID identity provider. Allure TestOps now processes the token refresh interval from the provider’s response.
• Improved the design and interactions with widget elements on dashboards.
• Increased the supported character limit in AQL filters.
• Improved the functionality of webhooks:
  • Added a default header when creating a webhook.
  • Added labels for automatically disabled webhooks. If Allure TestOps doesn’t receive a 200 status code from the external system after 10 attempts, the webhook will be automatically disabled.
  • Added support for assigned and project ID variables in the webhook query editor.
• Added the ability to choose the Exact Match operator in test case filters when the No value toggle is enabled.
• Optimized working with the new test case tree (feature flag “New test case tree”):
  • Added the ability to configure the interval between data migration jobs in milliseconds. The interval can be set up in the configuration files.
  • Optimized the data deletion job in case of structural changes to the existing tree.
  • Optimized the job for loading categories and test cases.
• Optimized processing of defect data from test results when closing launches.
• Optimized synchronization of custom fields between test cases and test results.
• Added other minor updates and fixes to Allure TestOps to optimize it and improve user experience.

Bug fixes

• Fixed the issue where the launch creator's name was shown in the manual test run history instead of the actual user who executed the test.
• Fixed the issue where not all of the user's projects were displayed on the My projects tab of the Allure TestOps home page.
• Fixed the issue where test result statuses were not updated in the launch widgets after being changed.
• Fixed the issue where selecting a filter match in the test case filters using Enter would add a duplicate filter.
• Fixed the issue where users could not delete defect automation rules created using regular expressions.
• Fixed the issue where users could not restart tests with the In progress status. Manual restart is now available via the bulk operations menu.
• Fixed the issue where users were unable to switch months in date filters for test cases.
• Fixed drag-and-drop issues in the test case tree (feature flag “New test case tree”):
  • Fixed the issue where moving a category would create duplicates of nested categories.
  • Fixed the issue where moving a category with nested items would place test cases outside the intended part of the tree.
  • Fixed the issue where moving a test case with two custom field values would delete both values. Now only the category the test case was moved from is removed.
• Fixed the issue where Allure TestOps would not start after an update due to a cryptoPassword parsing error.
• Fixed file routing in S3-compatible sharded storage: project buckets now work with the new key format (shard_x/***).
• Fixed the error that occurred when launching Allure TestOps with parameters enabled for RabbitMQ message reprocessing.
• Fixed the issue where uploading test results caused process deadlocks during attachment processing.

0 Votes