Vera 2024.2 Release Notes

Software version:Vera 2024.2

Release date: September 20, 2024

Explore the following sections for essential details about this release:

Version information

High-level Vera version 2024.2

Software Build

(You can verify this on the Versions screen in the Web Portal.

  • Web Portal: #

    (2024/MM/dd)

  • API Server: #

    (2024/MM/dd)

Resolved issues

In our latest version, we've fixed the following issues for you:

Issue Summary Notes
VS-4516 Incorrect Locking Group Causes Issues with Tosca Record Approvals Improves the display of Vera exceptions in qTest Records.
VS-4896 Projects drop down search cannot handle special characters Fixes search by project name on the records page by unescaping the project name for regex.
VS-4897 In the profile page updating email address with invalid email allows to save Improves the checks for invalid characters in the user's email address.
VS-4978 Signature Verification is not treated as an internal connection Fixed an issue where signature verification were not treated as an internal connection.
VS-4980 Connections with duplicate system urls can be created if the new connections has a slash at the end of the url I added a check if a System URL in a connection ends with or without a slash character.
VS-4991 Additional record statuses are displayed in Records Status dropdown on Records table Fixed an issue where Record Statuses were displayed that are not proper Vera record statuses. Additionally, any records that are not currently in an standard state will be migrated to a standard state.
VS-4993 Domain Administrator is displayed under Current System Roles Fixed an issue where was displayed the role 'Domain Administrator' on the User Profile Page for Domain Users.
VS-5021 User Profile Identity Provider "Cancel Changes" link is active after saving changes Fixed an issue where the button 'Cancel Changes' didn't switch back to 'Change Identity Provider' after resetting the form.
VS-5036 Identity Provider change without password fails with no toast message Fixed an issue where the error message on the component failed to appear when an incorrect password was entered.
VS-5055 Signature Verification does not validate against the correct record revision Signatures module was verifying signatures using current record. Now it is fixed to use the correct record revision which user was signed before.
VS-5144 Update Routes and Records Indexes Optimized some database implementations to provide better performance.
VS-5154 Routing of Tosca test executions fails when Tosca connection is not found Added the ability to ignore Tosca Connection errors when routing Test Runs related to Tosca Runs for approval. Clients must set the VERA_SERVER_IGNORE_MISSING_TOSCA_CONNECTION environment variable to True in the qTest Worker container in order to process Tosca Runs for approval without a Tosca Connection in Vera.
VS-5197 An Unhandled Exception occurs when a user who does not have access attempts to view No Sig Approved Record Fixed an issue on Record details page when the user accesses the Approval Routes Tab in a record that does not have a approval routes.
VS-5217 502 error is presented when user attempts to access Approval Routes tab of Draft Record Fixed an issue on the approval routes tab that was displaying an error when there were no approval routes.
VS-5288 Xray API (Server + DC) changed the structure of response for test execution Fixed an issue where the XRay Server API was updated to return different property names then expected. Vera will now support both XRay API versions.
VS-5292 Web Portal Dockerfile needs ca-certificates installed for clients who use self-signed certificates Added ca-certificates package installation to Web Portal dockerfile for clients who use self-signed certificates.
VS-5299 Web Portal does not support extra MongoDB Args Added support for Mongo Db Args as an environment variable in Web Portal configuration.
VS-5315 Signature reverification fails with a 500 error When re-verified, data verification returns a successful message.
VS-5358 Email notifications are not sent when a pending task is rejected after the first one has been approved

Fixed an issue where Route Owners and Authors would sometimes not receive an email notification when a route was rejected.

Fixed an additional issue where multiple emails could be sent to a Route Owner or Author if more than one Vera account was associated with an email address.

VS-5364 Print View - Draft records that have never been routed display "No signatures required..." Fixed an issue that was not displaying the signatures correctly on the record details.
VS-5374 Print View previous revision signatures displayed for draft revision Fixed an issue regarding signatures that was not displaying the approvers on the Print View tab.
VS-5376 Worker Audit History base image needs to be updated to allow using self-signed certs Updated the base image for the container.
VS-5380 Remove Link from External Defects in qTest Records Fixed an issue where external defects on a qTest record would create a broken link leading back to qTest's landing page. External defect keys are now displayed as the defect key without a link.
VS-5444 qTest Id numbers greater than Int32 max value prevent routing Fixed an issue where qTest entities could not be routed for approval when their ID was larger than the maximum 32 bit signed integer value.
VS-5451 Xray D/C (new version) call tests are not visible in Web Portal Fixed an issue where the call test step data of a test was saved empty in the database.
VS-5557 Vera-api-route-routeevents has a hard coded 120 second timeout for callbacks Fixed an issue where the default timeout was not configurable for the vera.api.routes.routeevents container. Now you can use the DEFAULT_HTTP_TIMEOUT environment variable to configure the timeout like other containers.
VS-5618 Users not displaying in Role Members table when Role contains Special Characters Resolved an issue in the Role Management table where users assigned to roles containing special characters were not displayed correctly.
VS-5642 Test Cases linked to a release via requirement should be unlinked when requirement is unlinked Added abillity to optionally cleanup inclusions when all other linkages to a record are removed.
VS-5653, VS-5627, VS-5626, VS-5462, VS-5461, VS-5454, VS-5438, VS-5424, VS-5411, VS-5146 Security Improvements Various Security Improvements

New features

Issue Summary
VS-2084, VS-2086, VS-4998, VS-4999, VS-5000, VS-5006, VS-5083 Users will see Vera time and date fields in their selected time zone.
VS-2199 Admin can set a field in the Records Management Policy as a date field. The field will be displayed in the user's configured time zone in the Vera Web Portal.
VS-2335, VS-4996 Users can set a timezone on their User Profile Page. The default setting is GMT.
VS-2382, VS-4699, VS-4982, VS-4983, VS-5164 Administrators can generate a User Roles Report. This report contains a list of all users along with their domain and system roles.
VS-4732, VS-4734, VS-4967, VS-5056, VS-5145, VS-5161, VS-5186 Create and Associate Linked Records When Routing qTest Test Case for Approval. Vera now shows the traceability between qTest entities rather than relying on qTest to view the relationship between entities. This includes creating releases in Vera based on the source system's record and adding the Vera records to the release.
VS-4733, VS-4735, VS-5067, VS-5068 Vera updates Draft records as they occur in qTest. Along with releases and record traceability, Vera will update records created from qTest as the qTest entity is updated in the source system.
VS-4747, VS-4748, VS-4749, VS-4750, VS-4751, VS-4752, VS-4753, VS-4754, VS-4755, VS-4756, VS-5024, VS-5038, VS-5062, VS-5111 Users and Administrators are notified via email when a user's account is updated.
VS-4771, VS-4818, VS-4886, VS-4887, VS-4888, VS-4890, VS-4891, VS-4892, VS-4893, VS-4894, VS-4895, VS-5120, VS-5121, VS-5155, VS-5156, VS-5157, VS-5158, VS-5159, VS-5193, VS-5221, VS-5248, VS-5282, VS-5289, VS-5303, VS-5304, VS-5442, VS-5453, VS-5456, VS-5526, VS-5556 Document Generation - Summary Reports. Users can now create Requirements Traceability Matrixes and Execution Summary documents with Vera. Supported output formats are docx, xlsx and pdf.
VS-4867 The Vera user interface was updated with Tricentis Standard components and branding providing an improved user experience. 
VS-5047, VS-5048, VS-5049, VS-5053 Administrators can configure record detail field order through the Records Management Policy. See the administration guide for more information on ordering fields.
VS-5091, VS-5092, VS-5093, VS-5094, VS-5097 Support Auditing of User Login and Logout
VS-5117 Prevent the System from adding Projects to the Default Domain. Projects were previously added to the default domain if there was no domain association at the time of routing a record.
VS-5205 Replace Bunyan Logger with Winston Logger for the Vera Web Portal
VS-5306 View List of Records Associated With Releases
VS-5345 Update Vera documentation link. The Documentation link in the Vera web portal now directs to the standard Tricentis Vera documentation page.
VS-5508, VS-5509, VS-5514 Update Linkages According to Record Changes. In accordance with record traceability, linkages on a Vera record are updated to match the source qTest record as its linkages change.
VS-5572, VS-5573, VS-5574, VS-5575, VS-5576, VS-5577, VS-5578, VS-5579, VS-5580 Create new Jira Issue in Vera with Jira-qTest integration. Vera will create corresponding records to be added to a release when integrated with Jira & qTest.
VS-5602 Allow Tosca Test Case route for approval if instance is configured to allow without Tosca connection

Docker image information

Repositories <repositories>
Tags
  • 2024.2.0

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 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-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
  • If a record is routed for approval that does not match any configured route templates, the user will see an error message indicating the record was proceed by Vera, but there was no Approval Route configured for the record.

  • In qTest the Approval Route field is updated with the message: "An error occurred while adding the specified record to the VERA route repository"

  • In Jira the Vera Panel will display: "Error Code 21 An unexpected error occurred while Vera was processing this record. Please contact an Administrator."

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-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-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-4830 CSV Importer does not Allow for Numbers in Full Name Field Attempting to import a user with a number in their Full Name will result in a failed import.
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-4904 Audit history page Vera ID filter cant work with special characters The Vera ID column on the Audit History page fails to handle filtering on some special characters. This results in an error message with no filter 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-5116 Domain Administrator is listed in System Roles on My Profile page Users listed as a Domain Administrator for any domain will also have Domain Administrator listed in their System Roles. Note: This does not allow the user to have any additional rights that they should not possess.
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.