Vera 2025.3 Release Notes
Software version:Vera 2025.3
Release date: September 24, 2025
Explore the following sections for essential details about this release:
Version information
| High-level Vera version | 2025.3 |
|---|---|
|
Software Build (You can verify this on the Versions screen in the Web Portal) |
|
Resolved issues
In our latest version, we've fixed the following issues for you:
| Issue | Summary | Notes |
|---|---|---|
| VS-7090, VS-7023 | Various Security Improvements | Fixed a security issue. |
| VS-7077 | Routing for approval can be broken if the default workflow does not exist | Fixed an issue where if the Workflows API was not running or the default workflow was missing, an exception would prevent records from routing for approval. |
| VS-7034 | Defects linked to a qTest Execution cause an exception in the qTest Worker | Fixed an issue causing errors to be seen in the qTest Worker Log file when Jira defects were linked to a qTest execution. Note: This fix does not affect any functionality. It removes a false flag that may have previously been seen in the log files. |
| VS-6957 | Refactor Workflow | Optimized Workflow to use Guide values instead of strings. |
| VS-6919 | Reset for Create workflow is not working | Fixed an issue where the Reset button on the workflow creation form failed to clear the Name, Description, and Owner fields and incorrectly disabled the Save button. |
| VS-6902 | The Scenario field in the Cucumber test and media type links (files, videos, images) are not properly formatted on the backend when a user logs in with the VERA Administration role | Fixed an issue where the Scenario field in the Cucumber test and media type links (files, videos, images) were not properly formatted when a user logs in with the System Administrator role. |
| VS-6898 | Users with old System Service Account claim cannot access Web Portal | Added a button to cleanup outdated system roles that caused issues for specific accounts when trying to log in to the web portal. |
| VS-6890 | Prevent Author Approval for Route Owner on Jira DC displays Approval Panel | Enhancement of logic for checking whether user is in author list. |
| VS-6881 | Vera displays incorrect message for unauthorized approvers | Fixed an issue where users where users were seeing "The record you are trying to access could not be found or has been deleted" instead of the correct "You do not have access do this item" message when navigating to an approval task that they do not have sufficient permissions to see. |
| VS-6856 | Typo found in Audit Details modal | Fixed a typo in the list of fields for the Update Password Policy action. |
| VS-5521 | Removing Domain Administrator roles from User claims list in DB | See details of VS-6898. This button only removes unused roles in Vera and will not have any effect on a user's current roles. |
New features
| Issue | Summary |
|---|---|
| VS-7076, VS-7075, VS-7014, VS-7059, VS-7012, VS-7011, VS-7010, VS-7009 | Domain Administrators and Route Owners can now assign approval tasks to specific users that have the task's role. Once reassigned, a Domain Administrator, route owner or the specified user can then reassign the task to a new user or back to the approval group as a whole. |
| VS-7057, VS-1952, VS-1951, VS-1950 | Users can now view tasks assigned directly to them in their Approval Queue. To filter on tasks assigned directly to you, use the filter to search by your username. |
| VS-7033 | As part of our ongoing efforts to migrate from Azure to AWS, we have updated the Job Service microservice to use Hangfire instead of RabbitMQ Delayed Exchange Plug-in. |
| VS-6961 | When an approval completes and the update to the source system (qTest or Jira) fails, Vera will no longer undo the approval. From now on, an administrator will be notified when the source system fails to update but the Vera approval was successful so that they may update the source system's record as needed. |
| VS-6879 | Update State related constraints to work with workflow states. |
| VS-6875 | Vera will now update records that are using a custom workflow when the source system's record is in a state designated as Editable. |
| VS-6818, VS-6746, VS-4210, VS-4209, VS-4208, VS-4206 | Technical Preview Vera now allows for the routing of qTest defects. Defects can also be configured to use a custom workflow similarly to the functionality introduced in Vera 2025.2 for requirements. |
| VS-6799 | Users can now link specific Record Types to a workflow through the Web Portal's UI. |
| VS-6184 | The Connections page in the Admin portal has been updated with new capabilities to support filtering and customization of the available columns. These changes are part of an ongoing effort to create a consistent look and feel across all tables in Vera. |
| VS-6614 | Workflows that are not designated as the default workflow and have no Records Management Policy or Record Type association can now be deactivated in the Web Portal. |
| VS-6529, VS-6528, VS-6526, VS-6516, VS-6515, VS-6514 | Multi-Task Approval Vera now allows for an approval route to be configured to allow a single user to approve more than one task for any given route. By default, this feature is disabled. |
| VS-6531, VS-6530 | To support the above feature for multi-task approval, the Vera approval queue page has been updated so that routes containing multiple tasks for the same role will display each task in the appropriate users' list of available tasks. |
Docker image information
| Azure repositories |
|
| AWS repositories |
|
| Tags |
|
|
How to upgrade |
For more details on how to upgrade, check out Upgrade the Vera Server applications. |
Known issues and limitations
| Issue | Summary | Notes |
|---|---|---|
| VS-139 | "Pending Tasks" field refreshes too slowly after route withdrawal. | The 'Pending Tasks' field in qTest and Jira doesn't immediately update when the record is approved or rejected in Vera. The cached values update when the user invokes a browser refresh. |
| VS-698 | VERA cannot create a qTest record if two fields in the record have the same name. | The VERA-qTest integration does not support importing records from qTest where the record has two fields with the same name. If such a record is routed for approval from qTest, then an error will occur. |
| VS-700 | User sees duplicate approval tasks for the same record in approval queue. | If an approval route contains two pending tasks for the same role (e.g. two Technical approvals) then an eligible approver will see both tasks in their queue. |
| VS-988 | Vera does not apply a default approval route. |
|
| VS-1064 | An error is displayed when splitting an issue in the standard VERA Jira workflow. | Atlassian’s create issue property prevents the splitting of a record. Combined with inconsistencies around workflow permissions, the error message displayed is currently unable to be addressed. |
| VS-2864 | User GUID is displayed instead of display name. | Custom fields with a user selection dropdown display in the web portal as the user’s ID rather than the user’s name. |
| VS-3346 | MongoDB cannot connect when password is not encoded. | MongoDB passwords must be URI encoded for MongoDB specifications. |
| VS-3984 | Handling empty bitmap image attachments properly in Record Details and Print View pages. | Empty bitmap images are displayed as a broken link in Vera. |
| VS-4359 | Scenario is not formatted on record detail for some cucumber tests. | Depending on the length of a Cucumber Xray Test, the scenario formatting may not display correctly in Vera. |
| VS-4899 | System Admin is able to edit a user's IdP username with special characters. | An administrator is able to update a user’s Identity Provider Username with invalid characters. |
| VS-4900 | User List in Role Management not working with special characters. | The user dropdown on the Role Management page fails to handle searching with some special characters. This results in no filter being applied. |
| VS-4903 | Filters in active user sessions page cant work with special characters. | The Username, Full Name and Last Access columns on the Active User Sessions page fail to handle filtering on some special characters. This results in no filter being applied. |
| VS-4992 | User Import does not assign Domain Viewer role when a domain without roles is specified. | Importing a user into a domain without defining role(s) will result in the user not being added to the domain, but the results file will show a successful addition to the domain. |
| VS-5352 | Approval Queue filter for Assigned Date does not return correct values when timezone is configured. | Filtering on a time in the approval queue may return incorrect results when the user has a configured timezone. |
| VS-5377 | Print View data runs off the side of the page. | Data with long single-word values may run off of the page or be truncated when printing a record. |
| VS-5378 | Footer in Print View does not show display time in user's set timezone. | The timestamp in print preview will not display in the user's Vera-configured timezone. This may cause confusion if a user's local machine is not configured to be the same timezone as their Vera user in the Web Portal. |
| VS-5410 | qTest Records with Custom Fields that duplicate a Vera System field will not route for approval. | If a qTest project has a custom field that matches the name of a Vera system field, the entity cannot be routed for approval. This is an unsupported configuration. The following fields cannot be created as custom fields for test cases and test runs: VERA ID VERA Approval Status VERA Pending Tasks VERA Rejection Reason VERA Approval Route. |
| VS-5566 | Status mismatch between Tosca and qTest when notification service is down during final approval | When notification service is down and a user attempts to apply final approval to a record, the update fails on the Tosca side but succeeds on the qTest side. This results in a Vera route that is still active (In Progress), the qTest record in Approved status, and the Tosca record in the IN_WORK status. |
| VS-5604 | User Roles Report gives error when filtering with special characters. | Filtering with special characters on the User Roles report may result in an error. |
| VS-5620 | Linked record navigation loses state after navigating to other pages and user then sees a blank page. | Users may be directed to a blank page after navigating away from the Linked Records tab of a Release, returning to the page and then selecting a record within the release. |
| VS-6341 | RMP upload fails when Schema ID is missing. | Schema ID is required in the Records Management Policy file in order to upload to the Web Portal. |
| VS-6395 | Filtering by Full Name doesn't work with special characters on the Available Users table of the Role Management tab. | Filtering with any operator besides “Equals” on Full Name in the Available Users table on the Role Management tab will result in an error. |
| VS-6452 | Images and Attachments not displayed properly in Activity History. | Images and attachments show broken links when viewing the record's details in the Activity History tab. |
| VS-6468 | Incorrect toast message displayed when adding a project with special characters to a domain. | When trying to add a project with special characters to a domain, users will see the following message:
"Cannot read properties of undefined (reading ‘statusCode’)” Please note that this is just an error with the message displayed and that projects rightfully cannot be created with special characters. |
| VS-6547 | Text for Xray Test Parameters for Jira DC is not displayed correctly in Vera. | The display of Xray Test Parameters is inconsistent between Vera and Jira. |
| VS-6580 | Print View PDF generated with Adobe PDF is missing data. | Adobe PDF does not render Vera records correctly in a PDF from Print View. Please use Save as PDF or Microsoft Print to PDF printer instead. |
| VS-6762 | Record Authors not being set correctly when a qTest user's name contains a comma. | When using the Prevent Author Approval feature, any names used to designate an author are incorrectly split when the user's name contains a comma. This causes the Prevent Author Approval feature to not work as intended. |
| VS-6844 | User Full Names with special characters, such as "ł" cause the web portal to crash. | The Vera Web Portal crashes when a user whose full name contains a special character attempts to log in. |
| VS-6849 | Embedded attachments are not displayed as expected in test steps. | Embedded attachments are not displayed correctly in test steps on the Record Details tab. |
| VS-6851 | Embedded attachments are not displayed as expected in test steps. | Embedded attachments are not displayed correctly in test steps on the Print View tab. |
| VS-6868 | "Disconnect Session" audit event not possible to achieve. | The Disconnect Session audit event is currently captured as Session Destroyed in the audit table. |
| VS-6901 | HTML Tables in a Test Step for Jira DC is not displayed properly in Vera | Tables originating from an Xray Test Step do not display correctly in Vera. |
| VS-7067 | Sub-records are displayed in the Record Type Workflows in RMP Policy Tab | Sub-record types that should follow their parent record type's workflow are displayed in the Record Type Workflows as editable. |
| VS-7083 | Routes are not cancelled when an error happens while the record is being updated | If a route gets created successfully in Vera but the update to the record is not completed successfully, the created route persists and can be seen in the users' approval queue, but cannot be acted upon. Currently, this issue is being seen when the workflows API is not returning the default workflow for clients. |
| VS-7181 | Remove Role not working from User Profile | Administrators cannot remove roles for a user from the User Profile - Domains & Roles tab. As a workaround, this action can still be performed by going to Domain Management - Domain - Role Management. |
| VS-7198 | Bulk user import does not allow + character | Administrators cannot import a user through the User Importer if the user has a + in their username. |
| VS-7205 | Filtering with Special Characters on Assignee results in 500 errors | Users may see unexpected errors when trying to filter using special characters on the Assignee field on the Approval Queue. |
| VS-7239 | Task Assigned to Deleted User Cannot Be Reassigned | If a task has been assigned to a specific user and the user is deleted, Domain Administrators cannot re-assign the task to another user or group. As a workaround, the record can be withdrawn from approval in the source system and re-routed. |
| VS-7259 | Html Tables in a Test Step for Jira DC is not displayed properly in Vera | Tables originating from an Xray Test Step do not display correctly in Vera. |