--- source_url: "https://docs.qameta.io/reference/release-notes/" title: "Release Notes | Allure TestOps Docs" mirrored_at: 2026-08-14T01:33:04.769Z host: docs.qameta.io cited_in_42a: true mirror_canonical: "https://index.42a.ai/docs.qameta.io/reference/release-notes/index" --- > **Original source:** https://docs.qameta.io/reference/release-notes/ Release notes are the source of truth for supported upgrade targets and for the product changes shipped in each Allure TestOps release. Upgrade only to the releases listed here unless a different route is advised by our [support team](https://help.qameta.io/). ## 26.2.2.3 - 8 July 2026 ### New Features - Allure TestOps now supports [HTTP exchanges](https://allurereport.org/docs/attachments/#http-exchanges) attachment type (`application/vnd.allure.http+json`) view. - Added native support for Forge-based Allure TestOps plugin for Jira Software Cloud. The plugin now detects Forge usage and adjusts its UI behaviour, including theme handling. ### Improvements - Added new [AQL attribute](https://docs.qameta.io/allure-testops/reference/aql/#available-fields) – **flaky** – for filtering unstable tests. This attribute works with both test cases and test results. - Updated the launches list layout so all metadata elements have fixed, predictable positions and are always visible. Multiple metadata elements stack vertically in the UI. - Updated single launch layout: each launch now displays a header with metadata, preserving context for users navigating to individual launches. - Minor UI improvements for clearer wording. - Added forward-compatible features for [Allure3](https://allurereport.org/docs/v3/) integration. - \[26.2.2.1\] enhanced launches lists layout for cases when launches have a lot of metadata. - \[26.2.2.1\] enhanced single launch layout, so users can chose whether to show or hide metadata of current launch. - \[26.2.2.1\] in test cases PDF export, the test cases in the document are not sorted by ID in ascending order. ### Bug Fixes - Fixed an error that created RabbitMQ queues with incorrect **durable** attribute during application initialisation. - Fixed incorrect behaviour during application startup when the storage type is defined as _S3\_ASYNC_. - Fixed the bug that prevented applied plain text filters from being visible to end users in test cases and test results lists. - \[26.2.2.1\] Fixed issue when issue links for test cases were created without actual link when linked via MCP. - \[26.2.2.2\] Fixed HTTP exchanges attachment type rendering layout. - \[26.2.2.2\] Fixed the issue when SaaS users saw Enter the license box when their subscription was past due. ## 26.2.1.8 – 4 May 2026 > Release 26.2.1.x adds new indexes to the largest database tables containing test results. This migration can be time-consuming, especially if you have accumulated test data over several years. > > During the upgrade to 26.2.1.x: > > 1. Disable all health probes > 2. Wait for the upgrade to complete > 3. Verify the instance is functioning correctly > 4. Re-enable health probes ### New features - We've supported [RabbitMQ quorum queues](https://www.rabbitmq.com/docs/quorum-queues), so there is no more version lock for the RabbitMQ usage. - We've supported usage of several S3 storages. Now for the on-prem deployed Allure TestOps different projects can use S3 buckets from different infrastructure elements which can be useful for corporate users when teams have their own dedicated infrastructure. - To use this feature you need to use at least the [Helm chart version 5.27.0](https://github.com/qameta/testops-deploy-helm-k8s/blob/main/charts/testops/CHANGELOG.md#5270) - We started implementing the brand new features from [Allure3](https://allurereport.org/docs/v3/) on Allure TestOps side. The following [Allure3](https://allurereport.org/docs/v3/) features will now work in Allure TestOps: - Allure3 [categories](https://allurereport.org/docs/categories/#allure-report-3) when tests are executed via `allure run` with enabled [Allure TestOps plugin.](https://github.com/allure-framework/allure3/tree/main/packages/plugin-testops) - Allure3 [named environments](https://allurereport.org/docs/v3/configure/#_6-environments) when tests are executed via `allure run` with enabled [Allure TestOps plugin.](https://github.com/allure-framework/allure3/tree/main/packages/plugin-testops) - Allure3 [global launch attachments](https://allurereport.org/docs/global-errors-and-attachments/#global-attachments), i.e. the entire **stdout** and **stderr** output generated by the test run when tests are executed via `allure run` with enabled [Allure TestOps plugin.](https://github.com/allure-framework/allure3/tree/main/packages/plugin-testops) - Allure3 [global launch errors](https://allurereport.org/docs/global-errors-and-attachments/#global-errors), i.e. any process-level exceptions encountered during the test run when tests are executed via `allure run` with enabled [Allure TestOps plugin.](https://github.com/allure-framework/allure3/tree/main/packages/plugin-testops) - Allure3 [quality gates](https://allurereport.org/docs/quality-gate/#run-allure-with-quality-gates-enabled) feature allowing to see whether a Quality Gate defined in the configuration of Allure3 has failed. To enjoy this feature tests need to be executed via `allure run` with enabled [Allure TestOps plugin.](https://github.com/allure-framework/allure3/tree/main/packages/plugin-testops) - Allure3-like [flaky test detection](https://docs.qameta.io/allure-testops/use-testops/execution-and-reporting/unstable-tests-detection/) — marking unstable test results with icons in the test results tree. - A test is considered unstable (flaky) in case there are at least 3 status transitions over the most recent 10 executions. - Allure3-like [test status transitions](https://docs.qameta.io/allure-testops/use-testops/execution-and-reporting/regressed-or-fixed/) — see at a glance which tests regressed, recovered, or appeared for the first time in a launch. ### Improvements - We are now blocking all unsafe (everything that does not use **https** or **http** protocol) links provided via markdown. - We've fixed potential CSV injections. This feature is configurable when Allure TestOps is deployed on-premises. - We've added new settings for integrations and web-hooks for SSRF prevention. - We've replaced old Errors tab of a launch with a new one with updated UI and Allure3 [categories](https://allurereport.org/docs/categories/#allure-report-3) support. - We've improved launch closing process. Now the event considers all background tasks required for proper test cases updates and generation. - We've moved all read-only transactions to the RO database replica allowing to unload main DB and improve its performance. - Applicable for on-premises deployments and premium cloud solution. - We've improved the test results processing performance. ### Bug fixes - We've fixed the login redirects issue that was always leading to redirecting of logged out user to main page instead of the provided URL. - We've fixed issue with the seeking feature for the video attachments. Now end users can play video from any part of the file using the UI controls. - We've fixed TMS sync issue that was leading to the absence of newly introduced test cases in the test runs created on 3rd party TMS side. - We've fixed MCP tool for test results. Now it works with launch ID properly and allows searching for the test results. - We've fixed S3\_ASYNC storage type behaviour. ## 26.1.1 — 4 March 2026 > An upgrade to release 26.1.1 is only possible after all prerequisite actions have been completed, including configuration updates and preparation of the database for the upgrade. For the details on the release upgrade preparations please refer to [this article.](https://docs.qameta.io/allure-testops/server/upgrade/notes/26-1-1/) > > Please do not upgrade your instance without reading the said [article.](https://docs.qameta.io/allure-testops/server/upgrade/notes/26-1-1/) ### New features - we've added built-in MCP server support as open beta feature. See details [here.](https://docs.qameta.io/allure-testops/reference/ecosystem/mcp-server/) - we've added new Launch graphs introduced in Allure3. New launch graphs are available in the Graphs tab of a launch created in Allure TestOps. ### Improvements - We've re-designed a bit the first administrator registration form which was a bit confusing before the refactoring. - We've added support for the uploading of the test results by Allure3 [Allure TestOps plugin.](https://github.com/allure-framework/allure3/tree/main/packages/plugin-testops#allure-testops-plugin) - New Allure3 upload generally decreases the data transfer towards Allure TestOps. - New Allure3 upload significantly decreases the usage of API for S3 solutions used as artefacts storage, which will decrease the TOC for paid S3 solutions such as AWS S3. - Generally Allure3 Allure TestOps plugin is still WIP, but can be used for simple uploads of the test results to Allure TestOps ver 26.1.1 and above. - We've improved the processing of data returned from an IdP when using Open ID for the authentication purposes. ### Bug fixes - We've fixed a bug where test results containing multiple parameters with the same key were not processed in the launch due to an unprocessed exception. - We've fixed an error that could lead to the bloating of one database table. - We've fixed the behaviour of the application when end user tried to see big CSV attachments. Now, if a user tries to view a very large CSV table, they will be prompted to download it instead as it was supposed to be done. ## 25.4.2 — 19 December 2025 ### Improvements - We've updated PDF generation engine for Test Cases PDF export, now the layout of the document is more stable and the rendering is being performed smoothly without exceptions and high memory consumption - We've introduced functionality allowing control of duration for storing of historical data (launches) on the BE side of the application. There is no UI for this at the moment. ### Security - We've fixed security vulnerabilities. - We've fixed the dependencies security vulnerabilities. ### Bug fixes - We've fixed error 415 when trying to trigger Bamboo pipeline from Allure TestOps side. We supported the updated API calls. - We've fixed an error preventing end users to be authenticated via SAML2 - We've fixed how SAML2 integration data is stored in the database. - We've restored lost functionality of the back-link creation in the created tests execution task for TMS integration with XRay Cloud. - We've fixed the issue when Xray integration was disabled due to negative response from XRay side due to the cookies expiration. ## 25.4.1 — 3 November 2025 ### Changes - We have temporarily disabled the import of the test cases from CSV files via UI. Please, [refer to this article](https://docs.qameta.io/allure-testops/use-testops/test-cases/import-test-cases/) to import test cases from CSV files. ### Improvements - We've added a feature allowing the usage of tokens instead of passwords for Bitbucket integration to support the recent changes on Bitbucket side. - We've added a feature allowing the usage of tokens instead of passwords for RedMine integration. - We've restored the issue link rendering for defects displayed in the launches overview section. - We've updated the default behaviour for the newly created jobs, so new jobs cannot be used for the tests execution right after creation. - We've added a feature and configuration parameter to the user's profile allowing the usage or the system font instead of the one delivered with Allure TestOps to ensure correct rendering of the characters with diacritic marks in the created entities. - We've added the support of ARM CPUs for the images of Allure TestOps. - We've restored the correct behaviour of test keys links in automated and manual test cases, now these can be always edited. ### Bug fixes - We've changed the PDF rendering engine to ensure the PDF generation based on created launch is not crashing and renders all the attributes and test results correctly. - We've fixed the emails validation for the invitees, the issue was preventing the invitations to the emails having many dashes. - We've fixed the authentication using SAML2 for the cases when the authentication process is initiated from IdP side. ## 25.3.4 — 30 September 2025 ### Improvements - We've added support for storing of SAML2 metadata files in the database for cases when IdP does not allow using URL to access the metadata. - We've added double click event support for steps and attachments in test results to manage their expanded/collapsed state. - We've changed default sorting for the jobs in the projects. - Now jobs are first sorted by their configuration parameter **Job can be used to run tests**, the ones that **can** go first. - Then inside each of 2 big groups jobs are sorted based on their id in ascending order. - We've changed the preview behaviour for big CSV tables, now if a CSV file is bigger than 400 kbytes, you need to download it. - We added warning and capability to cancel test cases trees deletion for the cases, when there are test plans using such trees to prevent the cascade deletion of such test plans. - We've updated configuration files for deb/RPM packages to support correct configs and all available datasources for optimised work with the database. - We've optimised DB requests to avoid possible DB locks. ### Bug fixes - We've fixed a bug that was preventing the rendering of test cases list when the duration sorting was selected for test results. - We've fixed the extremely narrow scroll bar width for test cases list. ## 25.3.3 — 03 September 2025 > If you are upgrading to this release from the releases older than 25.3.2, then please consider the information [provided for the release 25.3.2](#2532--26-august-2025) ### New features - We’ve introduced a configuration parameter that lets you bypass the idle session duration control set by the OpenID IdP, for cases where end users prefer to manage this setting within Allure TestOps. More details can be found in the [OpenID mapping](https://docs.qameta.io/allure-testops/server/configure/authentication/openid/) section. ### Improvements - We've updated dependencies to fix known vulnerabilities. ### Bug fixes - We've fixed a bug that was preventing the rendering of data for different data ranges in [Launch analytics widget.](https://docs.qameta.io/allure-testops/use-testops/results-and-analytics/dashboards/#available-widgets) ## 25.3.2 — 26 August 2025 > The upgrade to this release requires [alteration of the template settings in the configuration files.](https://docs.qameta.io/allure-testops/server/upgrade/notes/25-3-2/) > > Min. version of Helm chart supporting the release 25.3.2 is **5.25.0** ### New features - We're adding support for AWS SQS as an alternative to RabbitMQ when deploying in AWS infrastructure. ### Improvements - We've updated the integration with Jira Software Cloud to be consistent with the changes described in the Atlassian change log: [https://developer.atlassian.com/changelog/#CHANGE-2046](https://developer.atlassian.com/changelog/#CHANGE-2046) - Atlassian have deprecated some of API endpoints which absence causes issues with linking of test cases, launches and defects to Jira issues. We've updated the API endpoints accordingly to the described changes and Allure TestOps entities now can be linked to Jira issues without any problems. - We've updated dependencies to fix known vulnerabilities. ## 25.3.1 — 16 July 2025 ### New features #### Custom fields **Updated** the capabilities for configuring [custom fields](https://docs.qameta.io/allure-testops/use-testops/test-cases/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](https://docs.qameta.io/allure-testops/use-testops/test-management/tags-labels-layers-and-custom-fields/#admin-and-project-setup): - 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](https://docs.qameta.io/allure-testops/reference/aql/). This feature is available under the "AQL in filters" feature flag. #### Integration with ClickUp **Added** one-way integration with [ClickUp](https://docs.qameta.io/allure-testops/reference/integrations/issue-trackers/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](https://docs.qameta.io/allure-testops/use-testops/projects/#move-between-project-areas) 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](https://docs.qameta.io/allure-testops/use-testops/projects/project-notifications/): - **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](https://docs.qameta.io/allure-testops/use-testops/test-cases/#filter-conditions) 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. ## 25.2.6 — 5 June 2025 ### Bug fixes - **Fixed** the issue where the "Automation Trend" widget could not be added to the dashboard and returned an error with code 400. - **Fixed** the issue that prevented existing users from signing in to Allure TestOps when authenticated using an OpenID identity provider and the license limit was reached. - **Fixed** the issue where the selected sorting type in the **Test cases** section was reset after the user navigated to another section. - **Fixed** the issue where keyword search didn’t return results from automated test scenarios. Now the search includes scenario content. - **Fixed** the issue where reopening the **Test cases** section would reset the previously selected test case tree. - **Fixed** the issue where the project owner with the "User" global role couldn’t edit comments of other users in test cases. - **Fixed** the issue where the user held down Ctrl (for Windows) or Command (for macOS) and left-clicked a launch name, and the launch page opened in both a new tab and the current tab. Now the launch page opens only in a new tab. - **Fixed** the issue where the page reloaded automatically when the user attempted to rename a test case in the test case list. - **Fixed** the problem where searching for issues in the Azure issue tracker failed if the issue name contained special characters. - **Fixed** the problem that caused PDF export of a test case to fail if a link text was missing. ## 25.2.5 — 22 May 2025 ### Improvements - **Added** minor updates and fixes to Allure TestOps to optimize it and improve user experience. ### Bug fixes - **Fixed** the issue where test cases didn't load when the user clicked the **Load more** button in the test case list. ## 25.2.4 — 15 May 2025 ### Improvements - **Added** minor updates and fixes to Allure TestOps to optimize it and improve user experience. ## 25.2.3 — 24 April 2025 ### Bug fixes - **Fixed** the issue that occurred when attempting to update a job with a configured integration. ## 25.2.2 — 22 April 2025 ### Bug fixes - **Fixed** the issue where defect cards displayed the same set of automation rules instead of rules unique to each defect. ## 25.2.1 — 21 April 2025 > When upgrading the server version of Allure TestOps to 25.2.1, the application will run scripts once to create indexes on some of the largest tables in your database. This is necessary to improve Allure TestOps performance. > > Creating indexes on tables is a resource-intensive process, the execution time of which depends on the size of the tables in your database. During this process, the Allure TestOps instance will be temporarily unavailable. > > To avoid temporary downtime, you can run scripts in advance on the current version of your Allure TestOps instance. To do this, we strongly recommend that you read the [instruction for creating indexes](https://docs.qameta.io/allure-testops/server/upgrade/notes/25-2-1/), which provides step-by-step recommendations for administrators of the server version of Allure TestOps. If you follow the instructions before upgrading to version 25.2.1, you will be able to install the update without interrupting the operation of the instance — the scripts will not run again during the update. ### New features #### New home page **Updated** the Allure TestOps [home page](https://docs.qameta.io/allure-testops/use-testops/projects/#find-the-right-project-quickly), where users can access: - **My projects** tab: projects to which the user is added as a collaborator. - **Favorites** tab: projects that the user added to **Favorites** by clicking the star next to the project name. - **Browse all projects** link: all projects of the Allure TestOps instance are now available on a separate page. ![The updated Allure TestOps home page includes My Projects and Favorites tabs](https://docs.qameta.io/images/release-notes/v25/25.2.%D1%85/25-2-1-home-page-en.png) The home page now displays a project description and clickable statistics: - users with the “Owner” project role; - number of manual test cases, the icon leads to the **Test cases** section and opens the filter for all manual test cases; - number of automated test cases, the icon leads to the **Test cases** section and opens the filter for all automated test cases; - percentage of project automation, the icon leads to the **Dashboards** section; - number of launches in the project, the icon leads to the **Launches** section. To open the Allure TestOps home page, in the breadcrumb navigation, click the project name and select **Home** or click the Allure TestOps icon. #### Updated projects page **Updated** the [page with all projects](https://docs.qameta.io/allure-testops/use-testops/projects/#find-the-right-project-quickly) of the Allure TestOps instance: now it displays project description and clickable statistics, the list of projects can be sorted by project name and ID. ![The updated projects page contains the list of all available projects and extended information about them](https://docs.qameta.io/images/release-notes/v25/25.2.%D1%85/25-2-1-all-projects-page-en.png) #### New trees and filters in test results **Added** new [trees](https://docs.qameta.io/allure-testops/use-testops/test-management/project-trees/) and [filters](https://docs.qameta.io/allure-testops/use-testops/results-and-analytics/test-results/#sorting-and-filtering-test-results) to the **Launches** -> **Tree** section (the "New test case tree" feature flag): - **Updated** the interface and **added** new mechanics for working with trees: in an open launch for test results without status, left-click on the status to open a window for selecting the status, right-click on the tree to open menu for test results and categories. - **Expanded** the number of options for sorting test results in trees: you can sort by status, update date, test layer, test ID, alphabetical order and duration. - **Updated** the interface and **added** new filter operators: **Partial Match (OR)**, **Exact Match (AND)** and **Does Not Contain (NOT)** are available. - **Added** the ability to filter by empty attribute values using the **No Value** switch. - **Added** the ability to save filters. #### Email verification **Added** email verification to enhance the security of your accounts. After installing the update and signing in to the system, you’ll be prompted to confirm the current email from your Allure TestOps profile or provide a new one. ![Upon first sign-in to Allure TestOps after upgrading the instance, a window will appear prompting you to verify your email.](https://docs.qameta.io/images/release-notes/v25/25.2.%D1%85/25-2-1-confirm-email.png) Click **Continue** to receive a confirmation link at the specified email. Please note that the link is valid for 24 hours. If the link expires before you verify your email, you will need to request a new one. ##### **Verification when changing email in the user profile** **Updated** the logic for changing emails [in the user profile](https://docs.qameta.io/allure-testops/use-testops/personal-settings/#change-email): now after you enter a new email, a confirmation link will be sent to that email. If needed, you can resend the link or cancel the change. Only after you click the link and confirm the new email will it be reflected in your profile. ##### **Changing email via the Administration section** **Updated** the interface for changing emails of members and guests [in the **Administration** section](https://docs.qameta.io/allure-testops/administer/users-and-access/manage-members/): now a dedicated **Change email** menu option is used to assign a new email to a user. Additionally, user lists now display email verification statuses: - link sent, no more than 24 hours passed, but the email was not confirmed; - link sent, but more than 24 hours passed, and the email was not confirmed. Administrators can resend the link or cancel the email change if necessary. ### Improvements - **Improved** the code generation capabilities for test automation: expanded the list of supported programming languages and frameworks. - **Removed** the launch status from the breadcrumb navigation to avoid overloading the interface. - **Added** the ability to enable and disable filtering by date in the "Launch Trend (by date)", "Launches", "Last Launch Pie Chart" widgets. - **Updated** the interface for selecting assignees for test cases via bulk operations: now it is more convenient to select and remove assignees, the function of distributing test cases between assignees is more transparent. - **Added** the ability to deselect test cases and exit the test case creation mode within the tree using the Esc key. - **Modified** the process of handling errors from the database. Now error message with code 409 is displayed when there is insufficient data from the user side, in other cases the error with code 5xx is displayed. - **Optimized** the request for transferring data from test results to test cases when closing a launch. - **Expanded** GitHub integration capabilities: you can now [integrate GitHub as an issue tracker](https://docs.qameta.io/allure-testops/reference/integrations/issue-trackers/github-issues/) and link Allure TestOps entities to GitHub issues for more efficient test management. - **Added** a new parameter combination method for manual test cases — [Pairwise combinations](https://docs.qameta.io/allure-testops/use-testops/test-cases/parameters/). - **Changed** the instance activation flow when using a third-party identity provider: now to create an account and activate the Allure TestOps license, the first administrator must follow the link from the invitation sent to the email from the instance configuration file. - **Adjusted** the navigation and **added** other small changes to Allure TestOps to optimize and improve the user experience. ### Bug fixes - **Fixed** the issue that prevented integration with Yandex Tracker from being configured. - **Removed** the ability to edit metadata of deleted test cases: now to make changes to a deleted test case’s metadata, the test case should be restored first. - **Fixed** the issues that caused incorrect display of execution time for test case steps, as well as step and sub-step numbering in launches when exporting to PDF format. - **Resolved** the issue where the test case tree drop-down list displayed only 10 items. - **Fixed** the problem in GitLab and GitHub integrations where issue selection fields appeared empty when editing linked issues. - **Corrected** the problem where the parameter table in test cases expanded to the full width of the test case card and didn’t scroll. - **Fixed** the “Some issues are not found” error that occurred when importing test cases from CSV files. - **Adjusted** the color assignment logic in the "Test Case Tree Map Chart" widget. - **Fixed** the issue that prevented users from editing custom fields in automated test cases when the [**from\_test\_case**](https://docs.qameta.io/allure-testops/use-testops/test-plans-and-launches/upload-policy/) metadata source was enabled. - **Fixed** the issue where not all possible parameter pairs were generated when using the **All pairs** option for manual test case parameters. - **Fixed** the issue where step buttons were missing in test cases that were reassigned to another user. - **Fixed** the problem that prevented the administrator from inviting users with third-level domain emails. ## 25.1.4 — 26 March 2025 ### Bug Fixes - **Restored** POST binding support for authentication via SAML2 identity provider. - **Fixed** vulnerabilities in dependencies in the Allure TestOps image. ## 25.1.3 — 17 March 2025 ### Bug Fixes - **Updated** the Allure TestOps image: reduced its size and removed unused components. ## 25.1.2 — 10 March 2025 ### Bug Fixes - **Fixed** the display of webhooks: sensitive information is now hidden when viewing webhooks in project settings. ## 25.1.1 — 3 March 2025 ### New Features #### Webhooks in Allure TestOps **Added** the ability to send information about events from Allure TestOps projects to third-party systems using [webhooks](https://docs.qameta.io/allure-testops/use-testops/projects/project-notifications/). For example, you can set up integration with your work messenger and receive messages about the beginning and completion of launches, detected defects or creation of new test plans. #### Code generation for test case automation **Added** [code generation](https://docs.qameta.io/allure-testops/use-testops/test-cases/#generating-code-for-test-case-automation): the ability to generate code for automated test cases in supported programming languages directly in the Allure TestOps interface. #### New operators in filters **Expanded** [filter capabilities](https://docs.qameta.io/allure-testops/use-testops/test-cases/#filter-conditions) in the **Test cases** section ("New test case tree" feature flag): - **Added** the **Partial Match (OR)** and **Exact Match (AND)** operators, which provide the ability to filter test cases by partial or full match of selected attribute values. - **Added** the **Does Not Contain (NOT)** operator, which provides the ability to filter test cases by excluding selected attribute values. - **Added** the **No value** switch, which provides the ability to filter test cases by empty attribute values. Filtering by empty values works in combination with the **Partial Match** operator. #### Redesigned Launches section **Updated** the **Launches** section: it is now available without the feature flag and allows you to work more efficiently with launches and test results. **Replaced** the user profile page with the [user menu](https://docs.qameta.io/allure-testops/getting-started/account-and-profile/), which combines all user settings. The user menu allows you to: - view and edit profile information — name, avatar, email, password, and interface language are displayed in the sidebar, not on the separate page; - create API tokens to configure integrations with Allure TestOps via the API; - enable feature flags and preview Allure TestOps beta features; - select color themes for the workspace and the navigation sidebar. The **Administration** section has moved to the breadcrumb navigation. To access it, click the project name and select **Administration** from the menu that appears. #### Global cleanup rules **Added** a [predefined set of global cleanup rules](https://docs.qameta.io/allure-testops/administer/maintenance/cleanup-policies/#default-global-cleanup-rules) to new Allure TestOps instances. This applies to all Allure TestOps cloud instances, as well as Allure TestOps server instances deployed for the first time (without created projects). #### Encryption algorithm In the Allure TestOps settings, **added** the ability to select the encryption algorithm used when saving objects to the S3-compatible storage. #### Version history feature flag **Added** version history in test cases as beta feature ("Version history in test cases" feature flag): advanced versioning with the ability to store, compare and restore test case versions. To activate beta features, follow the [Activating beta features](https://docs.qameta.io/allure-testops/getting-started/account-and-profile/#activating-beta-features) instruction. ### Improvements - **Enhanced** the capabilities of the new test case tree ("New test case tree" feature flag): - **Added** the ability to change the status of a test case in the tree, without having to open the test case for editing. - **Added** a **Select all** button to select all test cases in the tree. - **Adjusted** the sorting logic of test cases: now the order of categories changes only when you select alphabetical sorting, all other sorting types affect test cases only. - **Updated** the navigation within Allure TestOps: - **Added** a button to return from the settings of an individual integration to the general list of integrations in the project settings. - **Improved** transitions between projects via the breadcrumb navigation: when switching to another project, the user is taken to the section that was open in the previous project before switching. - **Expanded** the breadcrumb navigation: now it displays the name of the open test case, defect, and shared step. - **Improved** the navigation in the project settings: in the breadcrumb navigation for the project settings added a separate drop-down list with subsections, in the navigation sidebar added two click areas for the project settings section (expand/open). - **Improved** the user experience in the **Launches** -> **Tree** section: - **Optimized** the view of parameters in test results: now parameters in a test scenario are hidden by default. - **Added** the ability to paste images from the clipboard into the test results scenario. - **Added** the ability to save filters in the **Launches** section. - **Adjusted** the logic of displaying issues from the issue tracker when importing test cases: now the imported test case displays links to issues directly linked to this test case. - **Updated** the TMS sync settings: now TMS sync will be automatically disabled in case of access problems. In the settings you can specify an email, to which the notification will be sent when TMS sync is disabled. - **Added** forced termination of a user session if their global role changes. After user signs in, a new session with the current permissions will start. - **Increased** the click area for opening attachments in test case scenarios. Attachments are now expanded when you click their title. - **Added** the ability to view test case scenarios in already open test case cards when the Allure TestOps instance is unavailable. - **Optimized** the connections in database tables that contain user account information to speed up processing of complex queries. - **Improved** the handling of time zone data in dashboards and its display on widgets, and reduced the length of intervals to further break down data in widgets. - **Optimized** the logic for selecting interface language when user signs in for the first time: now at first visit Allure TestOps uses the language set in the user's browser. - **Added** other minor updates and fixes to Allure TestOps to optimize it and improve user experience. ### Bug Fixes - **Fixed** the issue where after removing an AQL query from the widget, the wrong number of test cases was displayed and query validation error occurred. - **Fixed** the issue that occurred when exporting launch results to CSV format. - **Fixed** incorrect iFrame behavior in Jira that caused launch information to be displayed outside of the iFrame. - **Optimized** building the test case trees to speed up tree processing. - **Fixed** the error that caused elements with data to be displayed incorrectly in the **Launches** section. - **Fixed** the error that caused the test case tree to reload after user changed status, test layer, or cloned test cases. - **Fixed** the mapping of SortObject properties in Swagger, SortObject properties now match the described schema. - **Fixed** the error where parameters in scenario steps were incorrectly displayed in the test results. - **Fixed** the error where the test case ID was not displayed after renaming the test case in the test case tree. - **Fixed** the issue with the automated tests progress bar not displaying correctly in a launch. - **Fixed** the issue where the update time was displayed incorrectly after user updated a saved filter. - **Fixed** the issue that caused test result artifacts not being removed when using the API for instance or project cleanup. - **Fixed** the issue that caused content search to fail for shared steps. - **Fixed** the behavior of `api/testresult/bulk/resolve` endpoint where the endpoint allowed to change the status of automated tests. Now the endpoint correctly rejects requests to change parameters of automated tests and applies changes to manual tests only. - **Fixed** vulnerabilities in dependencies, updated org.springframework.boot to version 3.4.2. - **Optimized** data insertion and update operations to prevent database locking when processing queries. - **Fixed** the issue that prevented users with viewing and commenting permissions from adding comments in test cases. - **Replaced** the database connection pool for uploading test results using allurectl: now the uploader pool is used instead of the main pool. - **Fixed** the incorrect display of AQL fields in the “Automation Trend” widget: now the fields **Filter by test cases** and **Filter by launches** are not displayed when creating and customizing the widget. ## 24.4.2 — 26 December 2024 ### Bug Fixes - **Fixed** the issue with test case ID not being displayed after renaming the test case in the text case tree. - **Fixed** the issue in the configuration files for Docker Compose which prevented the TestOps instance from running correctly. - **Fixed** the issue which prevented users from adding widgets in the **Dashboards** section. - **Added** the [API for migrating tree data](https://docs.qameta.io/allure-testops/use-testops/test-management/project-trees#troubleshooting) to the new data structure. Now if test case trees are not displayed correctly, you can start migrating tree data to the new data structure using the API without having to edit the individual tree settings or turning off the “New test case tree” feature flag. ## 24.4.1 (previously 5.12.0) — 20 December 2024 > Starting with Allure TestOps version 24.4.1 (previously 5.12.0), we are implementing the new version numbers to simplify keeping up with releases. Now each version of Allure TestOps will be in the **YY.Q.X** format. ### New Features #### New Navigation **Updated** the design and functionality of [the navigation](https://docs.qameta.io/allure-testops/use-testops/projects/#move-between-project-areas) in Allure TestOps: - **Optimized** the size of the sidebar: it takes up less space now and can be hidden and expanded when needed. - **Added** the breadcrumb navigation at the top of the screen: now there is quick access to favorite projects and **Administration** section, users can navigate Allure TestOps sections via drop-down menu. - **Moved** the user menu to the top right corner of the screen. #### Updated dashboards > After upgrading to Allure TestOps version 24.4.1 (previously 5.12.0), the **Automation Trend** widget on dashboards will initially appear empty. Data for it will start being collected from the date of installation of this release once a day. **Removed** the **Analytics** section: all features of this section will be available in the **Dashboards** section. **Updated** [the **Dashboards** section](https://docs.qameta.io/allure-testops/use-testops/results-and-analytics/dashboards/): - **Changed** the approach to working with the **Overview** tab that was added to the project by default: it is now an editable dashboard. - **Updated** the dashboard creation process: dashboard can now be created from a template with a specific set of widgets or as an empty dashboard to be configured from scratch. - **Added** the ability to drag and drop tabs with dashboards: to do this, left-click a dashboard tab and drag it. The order of dashboard tabs will be updated for all project collaborators. - **Added** the ability to copy dashboards: an already created and customized dashboard can be copied to any project to which the user has access. - **Updated** interaction with dashboards and widgets via menu: now right-clicking a dashboard tab opens menu with settings of the whole dashboard, and right-clicking a widget opens widget settings menu. - **Updated** design of widgets and empty dashboards to optimize data display and dashboard customization. #### Test case trees and filters **Added** a feature flag to display new test case trees and filters in the **Test cases** section. This public feature flag is enabled by default for all users, you can disable it in the user profile. The updated [test case trees](https://docs.qameta.io/allure-testops/use-testops/test-management/project-trees/) and [filters](https://docs.qameta.io/allure-testops/use-testops/test-cases/#filtering-test-cases) allow users to: - drag and drop multiple test cases and categories at once within the tree; - create empty folders in the test case tree; - apply additional options for sorting test cases; - customize the test case tree in more detail for better performance; - search for test cases by text in their scenario. **Added** a section with [deleted test cases](https://docs.qameta.io/allure-testops/use-testops/test-cases/#deleting-and-restoring-test-cases): it contains test cases after deletion, they can be restored if necessary or deleted permanently. To access it, select **Trash** from the test case tree drop-down list. #### Feature flag “New launches list” **Added** new feature flag that activates the updated **Launches** section with the following improvements: - **Display launch duration time** — the launch status shows how much time has passed since it was started. - **Environment variables** — both names and values of environment variables are displayed in the launches list. - **Filtering by tags and environment variables** — clicking on the tag or environment variable automatically filters the launches list by the selected parameter. - **Updated progress bar** — the launch progress bar is now interactive. Clicking on the specific status color opens the test results filtered by the corresponding status. - **Defect viewing** — for each launch, a list of related defects is displayed with active links to view them. - **Updated filters** — the filter interface and functionality were improved. The feature flag is available to all Allure TestOps users. To activate it, follow the instructions in [Activating beta features](https://docs.qameta.io/allure-testops/getting-started/account-and-profile/#activating-beta-features). If you have any suggestions or feedback regarding the new feature flag, please submit a request to our support team at [https://help.qameta.io/](https://help.qameta.io/). ### Improvements - **Optimized** the process of deleting and restoring test cases. Now, when deleting test cases, custom field values are not deleted: after restoring a deleted test case, the custom fields in it will be filled in and you will not need to specify the values of custom fields again. - **Optimized** adding related issues from an issue tracker to a test case. Now, if Allure TestOps is integrated with only one issue tracker, its name is automatically filled into the **Issue tracker** field when editing the **Issues links**. - **Added** minor updates and fixes to Allure TestOps to optimize it and improve user experience. ### Bug Fixes - **Fixed** an issue in the **Launches** section when users with the Guest role could not see the **Compare** button. Now users with view-only permissions can compare test launches. - **Fixed** an issue that caused custom fields from other test cases in the project to be deleted when deleting test cases using bulk operations. The error occurred when a user selected all test cases in the tree, deselected some test cases and deleted the selected test cases using bulk operations. - **Fixed** the error display in test results. Now, when opening the result of an automated test, detailed text about the errors encountered during testing is shown in its scenario. - **Fixed** the issue where step progress was reset when reopening a test result if the user had previously selected the **Pass previous** option in the **Step run actions** menu in the test scenario. - **Fixed** the issue that caused Firefox browser to display outdated user profile image after uploading a new photo. - **Fixed** the error that occurred when renaming a custom field value from the test case list (test case tree) if that value already existed in the project. - **Fixed** the issue with text color that made text in test case status message blend with the background in Dark mode. - **Fixed** the issue with browser cache not being properly utilised that caused longer loading times for Allure TestOps sections. ## 5.11.5 — 30 October 2024 ##### 5.11.4 (server version) — 15 October 2024 ##### 5.11.3 — 27 September 2024 > Starting from release 5.11.3, Allure TestOps **will not** start if the PostgreSQL database server version is below 15. This release requires an update to the configuration files. > > Please refer to [the configuration update page](https://docs.qameta.io/allure-testops/server/upgrade/notes/5-11-3/) for details on the changes required before upgrading Allure TestOps to version 5.11.3. > Starting with Allure TestOps version 5.11, migration of test case trees to the new data structure is enabled. For the server version of Allure TestOps installation, this may lead to **increased database load** as the background migration takes several days to a week. > > The risk of data structure corruption is minimal. If you encounter problems with the migration, please contact [support team](https://help.qameta.io/). > > To continue working with the previous data structure, disable the "New test case tree" feature in the user menu in the [Feature previews](https://docs.qameta.io/allure-testops/getting-started/account-and-profile/#activating-beta-features) section. Please note that the data migration **will remain active** and may increase CPU load by up to 10%. ### Bug Fixes - **Fixed** the issue where opening a saved filter with values for the **Member** parameter reset those values and resulted in a 400 error. - **Fixed** the API request handling when an invalid token is used. Now it returns a 401 error instead of a 200 response. - **Fixed** the issue where test results did not save user-specified details about the execution of steps with expected results. - **Fixed** the incorrect display of test case statuses in the Jira plugin iFrame. - **Fixed** the distribution of database connections between the main pool and the pool used for data migrations within the database. - \[5.11.4\] **Fixed** the error “HTTP Status 500 — Internal Server Error” that occurred when attempting to authenticate users in Allure TestOps using Okta as the OpenID identity provider. - \[5.11.5\] **Optimized** API query `/api/evv/suggest` to improve database performance under high load conditions. - \[5.11.5\] **Updated** the versions of the plugins `io.spring.dependency-management` and `org.springframework.boot` used in Allure TestOps. ## 5.10.1 — 11 September 2024 ### Improvements - **Added** minor updates and fixes to Allure TestOps to optimize it and improve user experience. ### Bug Fixes - **Fixed** the issue when users running test cases with both empty and filled scenarios could see steps from other test cases in the results of test cases with empty scenarios within the same launch. - **Fixed** the text alignment in markdown fields from justified to left-aligned. - **Restored** the functionality of the Ctrl+C (for Windows) and Command+C (for macOS) keyboard shortcuts in test result scenarios. - **Optimized** the rendering of test results, thereby fixing the issue of their slow loading when processing large volumes of data. - **Fixed** the error "HTTP Status 500 — Internal Server Error" during failed user authentication in Allure TestOps using OpenID. Now, if users have errors in their OpenID configuration or encounter sign-in issues on the Allure TestOps side, users are redirected to the sign-in form. ## 5.9.0 — 27 August 2024 ### New Features #### Checking for complete user profile information: first name, last name, email To help us integrate notifications into Allure TestOps, it's essential to learn more about our users. After you sign in, we will ask you to update your personal information in user profiles if any part of it is missing. Please fill out the **Complete your profile** form with your work email, first name, and last name just once and then continue using Allure TestOps features. ![The Complete your profile page will appear when you sign in.](https://docs.qameta.io/images/release-notes/v5/5.9.x/5-9-0-complete-your-profile-form.png) ### Improvements - **Added** the ability to manage the duration of inactive user sessions via configuration parameters of the instance. - **Added** the ability for all Allure TestOps users to edit their profile information including name, last name, and email. Additionally, users can no longer reset their passwords through the user profile, but they can still do so via the sign-in form as before. - **Updated** the capabilities of the Jira plugin iFrame. If a defect is linked to a Jira issue, the related test cases and launches will now be displayed within the issue. ### Bug Fixes - **Restored** the automatic assignment of test results to the user who started executing the steps. - **Fixed** the incorrect display of column headers in the launches comparison table when these columns could only be viewed through horizontal scrolling. - **Fixed** the issue when an error in a nested step was duplicated in the parent steps in the uploaded test results. Now an error message is visible only in the step where the error occurred. - **Fixed** the problem when attempting to edit an issue link in a test case or test result would create a new issue link instead of updating the existing one. - **Fixed** the issue when automated test cases with scenarios generated from test results displayed unnecessary text about attachments in the test results. Now the scenarios in such test cases no longer include steps in the format `Attachment [ID] from TestResult`. - **Fixed** the display of the button for editing links in automated test cases when the permission for this editing is enabled in the meta data update policy. - **Fixed** the issue when changes to the full name of an automated test case were not reflected in its change log. - **Fixed** the incorrect handling of actions when pressing the Enter key on the numeric keypad. Now the Allure TestOps response is identical when pressing any Enter key, whether on the numeric keypad or the main alphanumeric section of the keyboard. - **Fixed** the issue that caused SVG attachments in scenarios of test cases or test results to download when attempting to expand the attachments. - **Fixed** the behavior of the **Environment** section in the **Filters** panel of test results. Now users can filter test results only by the names of environment variables used in the launch. - **Fixed** the unstable behavior of radio button filters caused by the loss of their default values in test cases, launches, and test results. - **Fixed** the excessive creation of records in the Redis database when using an authorization token instead of a bearer token for authorization API calls. ## 5.8.1 — 16 August 2024 ##### 5.8.0 — 13 August 2024 ### Improvements - **Added** minor updates and fixes to Allure TestOps to optimize it and improve user experience. ### Bug Fixes - **Fixed** the display of scenarios in test results for automated tests. Now scenarios are collapsed by default. - **Fixed** the issue when users couldn't send API requests using Swagger UI with Nginx configured. - **Fixed** the display of the test result options bar in closed launches. Now the buttons to rerun test results manually, mute them, and link defects are not available in closed launches. - **Fixed** the behavior of the environment variable value field during launch creation. Now when the user changes the name of an environment variable, the system resets its previous value. - **Fixed** the issue when scenarios generated from test results in automated tests could not be collapsed. Now users can manually collapse/expand individual steps of such scenarios. - **Fixed** the issue of duplicate test results in the response of the API request `/testresult/__search`. - **Fixed** the playback of MOV format videos in Google Chrome. - **Fixed** the launch name when creating a job run. Now the name field uses a default value that includes the launch date and time. - **Fixed** the issue when, during user authentication via OpenID, the restriction on roles synchronization was ignored, granting the user more privileges than allowed. - **Fixed** the issue of the empty test case window in Jira when integrated with Allure TestOps. - **Fixed** the issue with the first admin invitation email being resent every time the Allure TestOps instance is restarted. - \[5.8.1\] **Fixed** the issue when users couldn’t sign in via OpenID with Azure AD as the identity provider. ## 5.7.0 — 30 July 2024 ### New Features - **Added** ‘No assignee’ option to filters in the **Launches/Tree** section. Previously it was possible to filter only by known assignee — only tests with assignee were shown. ### Improvements - **Improved** the OpenAPI documentation for the Allure TestOps API. Now API documentation provides information about the most relevant path for API methods used in Allure TestOps. - **Added** minor updates and fixes to Allure TestOps to optimize it and improve user experience. ### Bug Fixes - **Fixed** the validation error issue with manual test result uploads. Now when the user selects different file type in the upload form, error message disappears. - **Stabilized** the behavior of the input fields for entering environment variables in the launch creation form. - **Fixed** the issue with resetting custom field name values when renaming custom fields, which occured when the user switched between the tabs before saving changes. - **Fixed** the incorrect behavior of the defect creation form resulting in the deletion of information entered by the end user in automation rule name and automation rule regular expression when attemping to alter the name of the defect. - **Fixed** the incorrect behavior of the test scenario comparison form when attempting to copy steps from test result scenario to the stored scenario. - **Fixed** the backend issue which resulted in 5xx errors for the end user when processing attachments with '%' at the end of the file name. - **Fixed** the issue with parameters of the test case scenario steps not being rendered in the test results. ## 5.6.4 — 23 July 2024 ### New Features #### Bulk operations with custom field values We’ve **redesigned the bulk operations** for custom field values. Now you can merge multiple custom field values into one and delete multiple values from custom fields using bulk operations in the **Project settings/Custom Fields** section. To merge multiple custom field values into one, in the **Project settings/Custom Fields** section open the custom field card, select the required custom field values, click **Merge** on the toolbar that appears when selecting multiple values, and set the name for the new value. All merged custom field values will be replaced with the new value in test cases. You can also assign the created value as default for new test cases with this custom field. To delete multiple values from custom fields, in the **Project settings/Custom Fields** section open the custom field card, select two or more values, and click **Delete** on the toolbar that appears. #### OpenID in Allure TestOps server versions We’ve returned user authentication via OpenID for server versions of Allure TestOps. ### Improvements - We’ve **redesigned the empty state screens** in the **Test cases**, **Launches**, and **Dashboards** sections. Updated empty states provide more clarity on how to interact with Allure TestOps. ### Bug Fixes - We’ve **fixed the ability to navigate within multi-line scenario steps** using navigation arrow keys on the keyboard. - We’ve **updated the error message** for cases when users launched automated tests that do not have a job assigned to them. Now the error text describes the problem in more detail and users are being navigated to the **Jobs** tab within the launch window. - We’ve **fixed the issue with AQL tooltip disappearing** when users hover over it and try to click the link in it’s description. - We’ve **fixed the issue with applying previously used names** to custom field values. Now you can rename custom field values and later return their previous names. ## 5.5.0 (cloud version) — 8 July 2024 ### New Features #### Notifications in trial period We’ve **added notifications about trial period** to help our users navigate licensing. Now you can see how many days are left before your Allure TestOps trial period expires, how to upgrade to a paid version, and who to contact to learn more about available pricing options. #### Formatted scenarios in Test results We’ve **refactored the scenario structure** to be able to display scenario formatting in the Launches section: steps in test result scenarios are displayed in Launches the same way they are displayed in the Test cases section. ### Improvements - We’ve **updated** the settings for users with administrator role: - Now the administrator's (the one created with the instance and usually having the username _admin_) password is not reset after Allure TestOps instance was restarted. - All administrators can see when the license expires and add new license key. - Administrators without name and email in user profile will need to provide this information after sign-in. - \[Server version\] Administrator’s email should be specified in the configuration file when starting a new instance, SMTP configuration is mandatory for all new instances. In existing instances, the administrator will be able to sign in using the previously created login/password combination. - We’ve **improved** the process of moving tests to another project, now only target projects where user has write permissions will be suggested. - We’ve **improved** the process of deleting attachments in **test results**. Now only attachments added to a test result as the Launch progressed can be edited and deleted. If the user deletes such an attachment in the attachment tab, it is also deleted from the test result's scenario. Attachments, that came from test cases, can’t be edited or deleted from test results. - We’ve **optimized** the performance when rendering test case scenarios with large number of steps. - We’ve **enhanced** filters in the Launches section, so they will display the suggested lists for tags only used in the scope of the current launch. - We **introduced** new feature for highly loaded systems deployed 'on-premises' allowing to split the datasources for upload process and getting the statistical information for dashboards, so now you can point the stats requests to a read-only replica, thus unloading the production database. - We’ve **returned and updated bulk operations** for custom fields. Now users can add and remove custom field values from the test case tree using bulk operations, which enhances the efficiency and ease of management. ### Bug Fixes - We’ve **fixed** the problem with searching for issues in Azure integration. - We’ve **fixed** the deletion process for stored scenarios (the ones you have from manual test cases when performing the automation) in automated test cases. - We’ve **fixed** the behavior in test scenarios resulting in scenario steps being deleted after users select all text in scenario step and press Backspace key. Now the scenario step stays intact and only selected text is deleted. - We’ve **fixed** the permissions selector in the Project settings/Access section, now all previously created access permissions are displayed. - We’ve **fixed** the issue with project name not being displayed when editing the TMS Export configuration settings. For previously configured TMS Export settings, users need to re-select project and save settings. - We’ve **fixed** processing of tags with spaces and special characters in Jira integrations. Now tags that aren't matching Jira's labels format requirements will be omitted and won't create unnecessary workload. - We’ve **fixed** the authentication exception behavior when processing authentication tokens. - We’ve **fixed** the issue with restoring previously deleted test cases. - We’ve **fixed** the issue where test results displayed custom fields deleted from the **Administration/Custom fields** section before creating the launch. - We’ve **fixed** errors caused by external system authorization in Allure TestOps. - We’ve **fixed** the issue related to displaying project participants and the inability to create projects for the first admin. ## 5.3.2 (cloud version) — 4 June 2024 ### Bug Fixes - We’ve **fixed** the issue with displaying test result trees in the Launches section. ## 5.3.1 (cloud version) — 3 June 2024 ##### 5.3.0 (cloud version) — 31 May 2024 ### New Features #### New profile page and UI themes We’ve **redesigned** the user profile page and **added** the ability to select the UI appearance theme: now you can switch between the light, dark, ands system themes. #### Updated deletion process for custom fields Now custom fields are deleted **in two steps**: 1. Remove custom field from all projects it has been added to previously, then delete this custom field from the list of active custom fields by using the **Delete** option in the custom field menu. It will be moved to the **Deleted** tab and disabled in all test cases. 2. In the **Deleted** tab, click **Delete permanently**. Custom field will be deleted from the system. After the custom fields are deleted, they disappear from test cases and test case trees. Test case trees that use the deleted custom fields can’t be selected. The two-step deletion process allows to make sure that deleted custom fields are not used in any projects and recover them if necessary. ![Deleting custom fields](https://docs.qameta.io/images/release-notes/v5/5.3.x/5-3-0-deleting-custom-fields.png) #### Required custom fields Custom fields can now be assigned **‘required’ status** independently for each project. To assign the ‘required’ status to custom field from the **Administration** section: 1. In the **Administration** section, open the **Custom fields** subsection and click the custom field. 2. Open the project menu next to the selected project and switch on the **Required field** toggle. Custom field will be marked as required in this project. ![Required custom fields - Administration](https://docs.qameta.io/images/release-notes/v5/5.3.x/5-3-0-required-cf-admin.png) To assign the ‘required’ status to custom field from the project settings: 1. In the project settings, open the **Custom fields** subsection and click the custom field. 2. Open the custom field menu and switch on the **Required field** toggle. Custom field will be marked as required in the current project. ![Required custom fields - project settings](https://docs.qameta.io/images/release-notes/v5/5.3.x/5-3-0-required-cf-project.png) In test cases, required custom fields are highlighted in red when empty. In filters, required custom fields are marked as required with a tooltip. ![Required custom fields in filters](https://docs.qameta.io/images/release-notes/v5/5.3.x/5-3-0-required-cf-filter.png) #### Filtering by empty values in custom fields We’ve **added** the ability to filter test cases by empty custom fields. #### Advanced options in cloning test cases We’ve **expanded** the list of actions for missing custom fields when cloning or moving test cases between projects. Now you can: - add missing custom fields to the target project, - map them to existing custom fields in the target project, - exclude missing custom fields from the resulting copy of the test case. We’ve also improved the UI to simplify the process of cloning test cases. ### Improvements - We’ve **made some UI improvements**: updated icons, buttons, and colours across the app. - We’ve **added** the confirmation for closing in progress launches. Now the users are warned about the consequences and can make an informed decision when closing in progress launches. - We’ve **updated** the UI in the **Launches/Test results** section. Now it follows the UI in the **Test cases** section. ![Updated Test results UI](https://docs.qameta.io/images/release-notes/v5/5.3.x/5-3-0-test-results-ui.png) - We’ve **improved** the processing for large amounts of data and now Allure TestOps supports: - data caching in the Dashboards and Analytics sections, - several data sources separately for loading/processing operations of test results and widgets, - separate configuration of the MQ listeners related to test results processing and post-processing. - We’ve **changed** the behaviour of CSV import. Now `allure_id` field is **skipped by default** in CSV import mappings. ### Bug Fixes - We’ve **fixed** the issue with Edit and Delete buttons shifting in automation rules with long Trace pattern. - We’ve **fixed** the issue when attempting to run automated tests without selected a job. Now job selection is mandatory. - We’ve **fixed** the UI bug with checkboxes being visible through search input. - We’ve **added** mandatory validation for assignees when running tests. - We’ve **fixed** the issue with Xray integration sync. - We’ve **fixed** errors with linking issues to Yandex Tracker. - We’ve **fixed** the issue with users being unable to fully clear search input in select component. - We’ve **fixed** the issue with test scenarios displaying duplicate steps with expected results. - We’ve **fixed** the issue with environment variables in the Launches section containing values that are not used in the current project. - We’ve **fixed** initial loading of options for the integration project select component. - \[5.3.1\] We’ve **fixed** the issue with deleting custom fields that were previously used in deleted test cases. Now custom fields are automatically removed from deleted test cases and can be deleted from the project. ## Migration from Allure TestOps 4 > For the server version of Allure TestOps, migration from Allure TestOps version 4.x to version 5.x or higher requires new configuration files and databases merging. > > The source of the configuration files and description of the parameters is described in the installation section for each type of the installation. The databases merging process is described in [this section](https://docs.qameta.io/allure-testops/server/upgrade/upgrade-to-5-x/). > > If you have any doubts or questions about the merging process, please do not hesitate [to consult the support team](https://help.qameta.io/). > > Migration from version 4 is only possible from release **4.26.5**. Using older releases will brick your system and lead to data loss. In this case, the support team won't be able to help with data recovery. ## 4.x For the release notes of Allure TestOps version 4.x, please refer [to this page](https://docs.qameta.io/allure-testops/reference/release-notes/4-x/). ## 3.x For the release notes of Allure TestOps version 3.x, please refer [to this page](https://docs.qameta.io/allure-testops/reference/release-notes/3-x/). © Qameta Software Inc. All rights reserved.