Vera 2026.2 Release Notes

Vera now offers a public API with API key management, rate limiting, and OpenAPI documentation. Site Administrators create and manage API keys in the Web Portal to integrate external systems with Vera securely.

Site Administrators can now configure SAML 2.0 single sign-on directly from the Web Portal, including identity provider management, certificate handling, authentication context settings, and audit logging.

Vera now detects and helps resolve status mismatches between Vera and connected Jira and qTest source systems from the new Record Integrity workspace. Administrators review mismatches, configure acceptable source statuses per workflow state, receive notification emails, and attempt automatic fixes.

Site Administrators can now view, resolve, and manage electronic signature verification failures in the Web Portal. Domain members see signature status on approval tasks, and Vera can rescan, edit, or filter resolved failures.

Various workflow management improvements in the Web Portal, such as clearer field validation errors, an enhanced Workflow Change Requests tab with filtering, and corrected display of sub-records in Record Type Workflows.

Vera now obfuscates sensitive data in Web Portal console output and in Web Portal and Vera API logging.

System Administrators can now use a GraphQL query interface to build custom queries that retrieve data from their Vera instance.

Vera automatically imports SAML SSO settings and certificates into the Web Portal database on startup.

The Approval Routes tab now displays the assigned approver for each approval task.

Various security improvements.

Vera now parses usernames that contain commas correctly when it builds user lists. This addresses issues found when the Prevent Author Approval feature processed the authors list.

Fixed an issue where an administrator couldn't reset passwords when a custom password policy was in use.

Fixed an issue where a task couldn't be reassigned if the current assignee was a deleted user.

A default policy change now takes effect immediately after you select the toggle.

Optimized MongoDB indexes in the vera-worker-traceability service.

Optimized MongoDB indexes related to the routes module.

Fixed an issue where some user actions didn't update the user's last access time, causing a premature logout.

Fixed an issue causing routing failures for new Jira Connections.

Fixed an issue where a user's task rejection could display on the wrong task if the user was a member of multiple approval roles.

Fixed prioritization of record imports by making sure draft qTest record imports are marked as draft.

Fixed an issue where Jira-qTest Requirements couldn't be routed for approval from Jira under certain circumstances.

Fixed an issue causing Vera to create more than one default domain on startup.

Fixed an issue where Jira-qTest Requirements received Vera Actions when they shouldn't.

Fixed an issue that caused qTest records that had previously been withdrawn or approved to get routed again.

Fixed an issue causing the password for the SMTP configuration to revert to the default value when another field on the Mail Settings form was updated.

Fixed an issue where the defects modal could be missing or empty for Xray records.

Fixed an issue where the footer in Print View overlapped with content on the page.

• Most print formats work on standard records, but for records with large numbers of executions and attachments, the attachments header may occasionally overlap with the attachment link for documents. To prevent this, print in "Letter" paper size.

• To support the fix, Vera requires Chrome or Edge version 131 or later. Earlier versions may show no footer on the printed copy.

Fixed an issue where roles selected with the Select all checkbox weren't saved correctly.

Added a longer graceful shutdown period to Vera Server to reduce issues caused by pod eviction during processing of long-running records.

Fixed an issue where execution links were incorrectly copied to a new record revision when a record was revised.

Fixed an issue where the Approve button was clickable more than once during bulk approvals.

Fixed an issue causing all links to linked records to go to the latest revision instead of the listed revision number.

Fixed an issue where the Linked Records table showed an empty value for some record types.

• veraserver20190209075900.azurecr.io/tricentis/vera-api-audithistory

• veraserver20190209075900.azurecr.io/tricentis/vera-api-connections-testconnection

• veraserver20190209075900.azurecr.io/tricentis/vera-api-documents

• veraserver20190209075900.azurecr.io/tricentis/vera-api-domains

• veraserver20190209075900.azurecr.io/tricentis/vera-api-jira-routeactions

• veraserver20190209075900.azurecr.io/tricentis/vera-api-public

• veraserver20190209075900.azurecr.io/tricentis/vera-api-qtest

• veraserver20190209075900.azurecr.io/tricentis/vera-api-recordintegrity

• veraserver20190209075900.azurecr.io/tricentis/vera-api-routes-routeevents

• veraserver20190209075900.azurecr.io/tricentis/vera-api-traceability

• veraserver20190209075900.azurecr.io/tricentis/vera-api-universaladapter

• veraserver20190209075900.azurecr.io/tricentis/vera-api-verification

• veraserver20190209075900.azurecr.io/tricentis/vera-api-workflows

• veraserver20190209075900.azurecr.io/tricentis/vera-query-engine

• veraserver20190209075900.azurecr.io/tricentis/vera-server-legacy

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-audithistory

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-carbone

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-documents

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-domains

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-jira

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-jobservice

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-qtest

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-recordintegrity

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-traceability

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-universaladapter

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-verification

• veraserver20190209075900.azurecr.io/tricentis/vera-worker-workflows

• veraserver20190209075900.azurecr.io/tricentis/vera-web-portal

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-audithistory

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-connections-testconnection

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-documents

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-domains

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-jira-routeactions

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-public

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-qtest

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-recordintegrity

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-routes-routeevents

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-traceability

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-universaladapter

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-verification

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-api-workflows

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-query-engine

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-server

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-audithistory

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-carbone

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-documents

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-domains

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-jira

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-jobservice

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-qtest

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-recordintegrity

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-traceability

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-universaladapter

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-verification

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-worker-workflows

• 030430646322.dkr.ecr.us-east-1.amazonaws.com/vera-web-portal

• 2026.2.0

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.

The Vera-qTest integration doesn't 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, an error occurs.

If an approval route contains two pending tasks for the same role (for example, two Technical approvals), an eligible approver sees both tasks in their queue.

If a record is routed for approval and doesn't match any configured route templates, an error message indicates Vera processed the record but no Approval Route was configured.

Atlassian's create issue property prevents the splitting of a record. Combined with inconsistencies around workflow permissions, the error message can't be addressed.

Custom fields with a user selection dropdown display in the web portal as the user's ID rather than the user's name.

MongoDB passwords must be URI encoded per MongoDB specifications.

Empty bitmap images display as a broken link in Vera Record Details and Print View.

Depending on the length of a Cucumber Xray Test, the scenario formatting may not display correctly in Vera.

An administrator can update a user's Identity Provider Username with invalid characters.

The user dropdown on the Role Management page fails to handle searching with some special characters. No filter is applied.

The Username, Full Name, and Last Access columns on the Active User Sessions page fail to handle filtering on some special characters. No filter is applied.

Importing a user into a domain without defining roles results in the user not being added to the domain, but the results file shows a successful addition.

Filtering on a time in the approval queue may return incorrect results when the user has a configured timezone.

Data with long single-word values may run off the page or be truncated when printing a record.

The timestamp in print preview doesn't display in the user's Vera-configured timezone.

If a qTest project has a custom field that matches the name of a Vera system field, the entity can't be routed for approval. This is an unsupported configuration.

When the notification service is down and a user applies final approval, the update fails on the Tosca side but succeeds on the qTest side.

Filtering with special characters on the User Roles report may result in an error.

Users may see a blank page after navigating away from the Linked Records tab of a Release, returning to the page, and then selecting a record.

Schema ID is required in the Records Management Policy file to upload to the Web Portal.

Filtering with any operator besides "Equals" on Full Name in the Available Users table on the Role Management tab results in an error.

Images and attachments show broken links when viewing record details in the Activity History tab.

Projects can't be created with special characters. The error message displayed is incorrect.

The display of Xray Test Parameters is inconsistent between Vera and Jira.

Adobe PDF doesn't render Vera records correctly from Print View. Use Save as PDF or Microsoft Print to PDF instead.

The Vera Web Portal crashes when a user whose full name contains a special character logs in.

Embedded attachments don't display correctly in test steps on the Record Details tab.

Embedded attachments don't display correctly in test steps on the Print View tab.

The Disconnect Session audit event is captured as Session Destroyed in the audit table.

Tables originating from an Xray Test Step don't display correctly in Vera.

If a route is created successfully but the record update fails, the route persists in the approval queue but can't be acted upon.

Administrators can't import a user through the User Importer if the user has a + in their username.

Users may see unexpected errors when filtering using special characters on the Assignee field in the Approval Queue.

Tables originating from an Xray Test Step don't display correctly in Vera.

The Execution Summary report only generates with Draft records in the resulting document.

Test step attachments don't display for test executions or sub-test executions. Only attachments on the execution or sub-test execution display for these types of records.

Using special characters in the filter on any column of the Workflow State Mapping Results table results in a page refresh with no filter applied.

Adjust margin or page sizes to prevent cutoff. Minimum margins resolve the issue.

In audit history, the Old Value for policy detail changes (name, description, owner) isn't accurately displayed. As a workaround, search through the audit history by the policy ID.

Filtering with Equals, Does Not Equal, and Is Any of returns incorrect results.

If a user logs in with a different case than the username stored in the database and changes their timezone, the change doesn't take effect in Print View until the user logs out and logs back in.

Changing the source system in the middle of creating a new connection may save information from before the change. To see the information again, change back to the originally selected source system.

Some Xray Test Step Attachments don't show in the Vera Web Portal. As of this release, the Attachment button at the test step level and copy and paste don't work.