Vera 2026.1 Release Notes

Vera workflows now drive status transitions for qTest Requirements and Defects through an Action control. Configure approval for qTest requirements and qTest defects.

Route Owners and Domain Administrators can now assign approval tasks to specific individuals (Named Approvers) for clear accountability. Optionally require named assignment by policy, route template, or approval task.

Assign workflows at the Record Type or Policy (RMP) level with safe state mapping and approvals for changes to workflows on existing records. Check out Link workflows to Record Types.

Domain Administrators can now view all approval task assignments from the approval queue.

Vera now sends notification emails when approval tasks are reassigned.

Added author matching for qTest Requirements and Defects.

Route Owner information is now included in the API request when routing for approval.

Full-screen image attachments in Print View are now enlarged so they can be inspected in a PDF.

Vera logo harmonization across multiple platforms.

Users can now assign approvers to qTest records.

Jira Cloud now supports importing Jira records into Vera.

Jira DC administrators can now define Jira statuses that can transition to Routing for Approval.

Various security fixes.

User domain membership verification is now centralized in a utility class. Targeted endpoints use this class to check permissions.

Various index improvements.

Fixed an issue where the approval dialog closed before the approval finished.

Fixed an issue where users without domain access could access records through task or approval assignment links.

Records now correctly change status even when two routes are used.

Latest revision default workflow now updates with new workflow ID and name values.

Fixed an issue where users couldn't remove a workflow from a Record Type on the Record Type workflow tabs.

Improved memory footprint of the qTest integration by loading attachments after loading records.

Jira webhooks now work with custom workflows, including those with multiple approval routes.

PreventAuthorApproval value is now checked through the Approval Route instead of the route template.

Once a requirement is approved, it can no longer be deleted through the UI or API, even after revision.

Batch editing of qTest requirements and defects in a Vera locked state is now prevented.

Fixed an issue where the first page of a Print View PDF was blank.

Custom workflows now respect the proper final state for any route and create a revision entry for that route.

When a task is cancelled or rejected, Vera now notifies the assigned user. If the task isn't assigned, group notifications are sent if enabled.

Fixed an issue where the revision number was cleared after withdrawing the approval route.

Uploading a new policy with empty strings as default workflow ID and name now works without errors.

When no records match the record type during a Workflow Change Request, the system now displays the correct message.

Activity History now correctly shows who performed each transition.

Improved efficiency when routing records for approval.

Implemented import tokens so only one import can occur at a time, preventing collisions.

Approval buttons now display correctly for Named Approvers.

Prevented unnecessary retries caused by unexpected data or message ordering.

Fixed an issue where Vera used the default RMP instead of the configured RMP for the domain.

Fixed updating and routing of records when only the authors or linked records change.

Fixed an issue that prevented routing for approval from any status other than Draft.

Fixed record replacement so there's no window where the record doesn't exist.

Updated Gainsight logic to send the correct environment ID.

Limited updates to records when qTest sends update webhooks for records that haven't changed.

Fixed an issue where a record could be updated in a non-editable state.

Migrated the Web Portal build from npm to pnpm.

Verification now updates the signature verification status successfully.

Fixed parsing of JWT tokens when the authentication token is present multiple times.

Fixed the recording of record hash failures in verification to display the correct error message.

Records from the records repository now get their locations attached correctly.

Fixed an issue where some unexpected 403 errors occurred.

Fixed a build issue that caused incorrect display after reassignment.

Reworked database indexes for the Records module for better performance.

Updated queries so indexes are used properly in MongoDB.

Test Connections and Route Events microservices now re-register on restarts.

Enhanced logging for the web portal to add console output.

Fixed an issue where multiple activity history entries were recorded even though the record didn't change.

System variable is now retrieved from Connections and stored and returned properly.

HTTP Requests with multiple Authorization token values now use the first value.

Various index improvements.

Fixed an issue where qTest Defects couldn't be rejected in Vera.

Fixed an issue where certain error conditions caused the web portal to not display SSO errors properly.

Fixed an issue where some domain roles couldn't be removed from the Edit User page.

Cleaned up code to follow standards and fix warnings.

The Record Type Workflows page now only shows Record Types with overridden workflows. Added dropdowns to associate record type and workflow.

• 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-qtest

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

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

• 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-traceability

• 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-qtest

• 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-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-traceability

• 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.1.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.

When using Prevent Author Approval, names with commas are incorrectly split. This causes the feature to not work as intended.

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.

If a task is assigned to a user who is then deleted, Domain Administrators can't reassign it. As a workaround, withdraw the record from approval in the source system and re-route.

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.

The change to default policy isn't reflected immediately. Refresh the page to see the updated toggle.

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.