Vera 2025.1 Release Notes
Software version: Vera 2025.1
Release date: March 26, 2025
Explore the following sections for essential details about this release:
Version information
| High-level Vera version | 2025.1 |
|---|---|
|
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-4830 | CSV Importer did not allow numbers in the full name field. | Fixed an issue that blocked numeric characters in the full name field during CSV import, even though they are allowed in the UI. |
| VS-4904 | Vera ID filter on the Audit History page did not support special characters. | Fixed an issue that prevented filtering by Vera ID when special characters were used. |
| VS-5116 | Domain Administrator role appeared under System Roles. | Fixed an issue where a domain-specific role was incorrectly listed as a system-level role on the My Profile page. |
| VS-5646 | Generated timestamp overlapped titles in print view. | Fixed an issue where the footer in the Record Details print view overlapped content when generating PDFs. |
| VS-5662 | Cucumber scenario formatting was missing in the activity history. | Fixed an issue where formatting was not preserved in the Scenario field of the activity history view. |
| VS-5851 | Rich text from XRay did not format correctly in Vera. | Fixed an issue that misconverted Jira rich text into HTML, causing incorrect formatting. |
| VS-5897 | IdP errors caused the Web Portal to crash. | Fixed an issue that caused crashes when identity provider errors were not handled correctly. |
| VS-5909 | Vera did not support multiple XRay connections. | Fixed an issue that prevented users from creating multiple XRay connections using the same server URL. |
| VS-6007 | Jira-qTest requirements remained in the qTest domain after routing. | Fixed an issue where requirements were not transferred to the correct Jira project domain when routed for approval. |
| VS-6022 | Users could create domains without a name. | Added validation to prevent creating or updating domain names with empty, null, or whitespace values. |
| VS-6023 | Owner dropdown in the Create New Domain modal showed limited users. | Fixed an issue that limited the owner dropdown to the first 25 users. |
| VS-6043 | Vera records failed to route when qTest users were missing email addresses. | Fixed an issue where records could not be routed if Prevent Author Approval was enabled and qTest users lacked email properties. |
| VS-6056 | Jira integration did not match qTest requirements to the correct author. | Fixed an issue where authors were incorrectly matched during Jira-to-qTest requirement creation. |
| VS-6087 | Users could not save connection changes when a client certificate was present. | Fixed an issue that blocked updates to form fields if a certificate file was already uploaded. |
| VS-6103 | Approval window froze after incorrect password entry. | Fixed an issue where entering a wrong password locked the UI by keeping the loading spinner active and disabling the button. |
| VS-6104 | XRay test case could not be routed after test executions. | Fixed an issue that caused a NullReferenceException when routing a test case after at least one test execution had already been routed. |
| VS-6109 | Broken sync created a Vera record using incorrect RMP configuration. | Fixed an issue where failed syncs from Jira/qTest created records with the wrong record type. |
| VS-6224 | Email notifications used incorrect URLs for Jira-qTest requirements. | Fixed an issue where URLs in emails pointed to the wrong location for Vera. |
| VS-6230 | Versions page showed unsorted and duplicate microservice projects. | Fixed an issue with sorting and duplication in the Microservices section. Projects are now sorted alphabetically. |
| VS-6258 | MongoDB operations did not retry after failure. | Added retries for MongoDB operations when timeouts or queue issues occurred. |
| VS-6289 | Navigation menu was hidden by filter options. | Fixed an issue where filter dropdowns covered the left navigation when expanding menus. |
| VS-6293 | qTest records did not include issue keys in record names. | Fixed an issue where qTest test cases and runs were missing the issue key in their associated Vera record names. |
| VS-6316 | Vera did not send custom headers when authenticating with qTest. | Fixed an issue where headers and certificates were not sent as expected during authentication. |
| VS-6348 | Test step values in Vera did not match qTest. | Fixed an issue where custom dropdown fields in a qTest test step displayed a numerical value instead of the correct field value. |
| VS-6439, VS-6464, VS-6478 | Security improvements. | We performed some background changes to improve the overall security of Vera. |
New features
The following new features and improvements are available in this release:
| Issue | Summary |
|---|---|
| VS-5035 | Added support for multi-select field constraints in qTest workflows and approvals. New constraints include List Field Contains Any Of and List Field Contains All Of. |
| VS-5608 |
Records now display the release in the breadcrumb. The browser back button supports navigation through previously selected tabs on a record. |
| VS-5838 | The left navigation bar can now be pinned. Pinning shifts main content to avoid being overlapped. |
| VS-6005 | Vera now supports custom names for the Tosca Test Case Report using the VERA_TOSCA_TEST_CASE_REPORT_NAME environment variable. |
| VS-6041 | A new Projects column has been added to the Domain Management page. Admins can filter projects using the “includes any of” operator. |
| VS-6093, VS-6094 |
Improved load times when searching records. The Domain column is now filterable on the Records page. |
| VS-6019, VS-6079, VS-6080, VS-6312 |
Projects can now be moved between domains. Associated records are updated to reflect the new domain. |
| VS-6090, VS-6091 | Improved loading performance when filtering the Approval Queue. |
| VS-6144, VS-6145 | Vera now creates required document generation folders automatically at startup. |
| VS-5414 | For security reasons, accounts with the System Service Account role can no longer sign in to the Vera Web Portal. |
| VS-3598, VS-6267 | Record Details and Print View now align visually with other Tricentis products. Print View supports incremental loading for large records. |
| VS-6028, VS-6030, VS-6031, VS-6032, VS-6033 | Admins can now audit actions taken on policy files. These actions appear in the Site Administration Audit History. |
| VS-2811 | Policy Set creation is now logged in the Site Administration Audit History. |
| VS-3324 | Updates to the Password Policy are now tracked in audit logs. To see a full list of available audit log actions, see the Site Administration Audit History section of the What's New page or the Audit History page. |
| VS-6131, VS-6132, VS-6154, VS-6349 | The verification service has been migrated to microservices: vera-api-verification and vera-worker-verification. These are required for upgrades to 2025.1. |
| VS-6150, VS-6202, VS-6203, VS-6204, VS-6205, VS-6206, VS-6212 | UI tables have been standardized for consistent formatting and layout across the platform. To see the full list of upgrade tasks, check out Upgrade Tasks. |
| VS-6137, VS-6218, VS-6233, VS-6237, VS-6238, VS-6244 | Domain management has been migrated to microservices: vera-api-domains and vera-worker-domains. These are required for upgrades to 2025.1. |
| VS-6016, VS-6017, VS-6018, VS-6020, VS-6021, VS-6083, VS-6084, VS-6085, VS-6086, VS-6339 | Improvements made to how Vera stores domain metadata for records and routes. This enhances scalability and performance. |
Docker image information
The following Docker images are available in this release:
| Repositories |
|
| Tags |
|
|
How to upgrade |
For more details on how to upgrade, check out Upgrade the Vera Server applications. |
Known issues and limitations
The following known issues and limitations are available in this release:
| 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-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. |