Vera 2023.2.3

Software version: Vera 2023.2.3

Scheduled release date: 08 December 2023

This file provides information about Vera 2023.2.3:

Version Information

High-level Vera Version

2023.2.3

Software Build

(Can be verified on the "Versions" screen in the web portal.)

Web Portal: 2020

(2023/12/08)

API Server: 1.8.1.0

(2023/11/20)

Resolved Issues

Key

Summary

Notes

Key

Summary

Notes

VS-4597

Security Improvements

Security Improvements

Docker Image Information

Repositories

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

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

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

veraserver20190209075900.azurecr.io/tx3/vera-web-portal

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

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

Tags

  • 2023.2.3

How to Upgrade

See  https://tx3.atlassian.net/wiki/spaces/V20232/pages/298129439 for instructions

Known Issues and Limitations

Key

Summary

Known Issue Details

Key

Summary

Known Issue Details

VS-139

"Pending Tasks" field refreshes too slowly after route withdrawal.

The Pending Tasks field in qTest and Jira is not immediately updated when the record is approved or rejected in VERA.  The cached values are updated when the user invokes a browser refresh.

VS-447

User Administrator role can see Signature Verification Failure Report and Re-verify

A User Administrator can access the Signature Verification reporting section of the Administration Portal.  This feature should be limited to System Administrators.

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 DevOps does not apply a default approval route

If a record is routed for approval that does not satisfy any configured route templates, the user will see "VERA is trying to start the approval route" rather than a descriptive error containing the reason why the route was not started.

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-1065

A misleading error message is displayed when VERA cannot apply a final approval

VERA will display a misleading error message when it fails to transition a Jira issue in the workflow.  The error message displayed to the user will indicate that there is a connectivity problem, even if it's actually a configuration problem. 

VS-1293

Final approval fails when Jira projects are configured with a Signatures field

VERA will attempt to write the entire approval route to the Jira Signatures field if the field is present in the Jira project. If the approval route contains over 255 characters the Approval will fail since VERA is attempting to write over 255 characters to the field.

VS-1591

Password content can break qTest integration

Using a colon character (":") in the qTest Service Account password causes the qTest integration to fail. The colon character (":") is not supported and should not be used in service account passwords.

VS-2156

Domains do not display in approval queue if the name begins with $

Domains that begin with a special character may not appear in the approval queue. Records for the domain will still be displayed but the domain column will appear as empty.

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. See link for more details: https://www.mongodb.com/docs/manual/reference/connection-string/

VS-3382

Role members list is not automatically refreshed when a new user is added to a Role

When adding a new user to a Role, the Role members list is not automatically refreshed, requiring the user to click the refresh table button

VS-3405

Some special characters don't work in all columns search on Approval Queue page

Filtering may return either an error or all records when attempting to use special characters when searching in the Approval Queue.

VS-3410

Some special characters don't work in all columns search on User Management page

Filtering may return either an error or all users when attempting to use special characters when searching in the User Management page.

VS-3960

Defect Link is not present in Vera for qTest records

For qTest records, the name of the defect under the defects section is displayed as plaintext rather than a link to the defect.

Note: The defect can be navigated to by opening the defects modal and clicking the link on the defect name.

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-3993

Cannot re-route/withdraw approval for a record that has no domain association

A record that has previously been routed for approval at least one time cannot be re-routed or withdrawn from its current approval without its corresponding project being associated to a domain.

VS-4004

Users are not returned to login page after session timeout

When a user's session expires, they are not redirected to the login page. They will remain on the current page until they attempt to navigate to another page, which will result in an error.