Vera 2024.3 Release Notes
Software version: Vera 2024.3
Release date: December 13, 2024
Explore the following sections for essential details about this release:
Version information
| High-level Vera version | 2024.3 |
|---|---|
|
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-5910 | Options missing from Approval Policy and Records Management Policy drop downs on Policy Set Details | Fixed an issue that did not display all approval policies and record management policies in the Policies Tab on Policy Set Details. |
| VS-5889 | Version and Build Date are Swapped on Versions Page | Fixed an issue where Build Version and Build Date were swapped on the Vera Versions page. |
| VS-5840 | Jira Issues that are synced to QTest do not get associated with Record Type based on Jira | Used the location information from Jira when routing. |
| VS-5815 | User Session Terminates Before Inactivity Modal Appears | Fixed a bug where the inactivity modal didn't appear before the logout. |
| VS-5788 | Xray Steps are Missing with List Type Custom Fields | Fixed an issue where Xray Test Steps were missing on a record when using List Type Custom Fields on Test Steps in Xray for Jira DC |
| VS-5784 | RTM report does not contain requirements in the release that are not covered by Test Cases | Added all requirements to RTM, regardless of presence of test cases/test runs. |
| VS-5759 | Document Types not working importing correctly on migration | Fixed an issue preventing document types from importing successfully on startup |
| VS-5690 | Multiple Records are created when a Jira-qTest Requirement is Immediately Routed for Approval | Fixed an issue multiple records could be created when using Jira-qTest requirements |
| VS-5661 | Attachment source is broken for a previously approved revision of a record | Record revisions Broken Image/File links fixed with icons |
| VS-5607 | New modules and micro services versions not showing in web-portal | Updated the versions page to include new modules and microservice versions |
New features
| Issue | Summary |
|---|---|
| VS-5878, VS-5841, VS-5833, VS-5794, VS-5785, VS-5743, VS-5610, VS-5599, VS-5597, VS-5596, VS-5595, VS-5594, VS-5593, VS-5592, VS-5591, VS-5590, VS-5589, VS-5588, VS-5587, VS-5586, VS-5585, VS-5726 | Vera front end has been reworked in Vite. Various improvements to the UI of the Vera Web Portal for consistency and alignment with other Tricentis products. |
| VS-5806, VS-VS-5637, VS-5636, VS-5635 |
Improvements to qTest-Tosca-Vera (QTV) Integration. The integration can now be set to attach Tosca reports on Tests and Executions in Vera rather than displaying the individual steps on a record. Getting this report reduces the amount of API calls made to Tosca. |
| VS-5219 | Logins and Logouts for users are now visible in the Vera audit log. |
| VS-5887, VS-5708, VS-5707, VS-5706, VS-5705, VS-5704, VS-5703 | Vera now supports using Jira fields to map a user in Jira Data Center to a user in Vera. This can be used to configure the Prevent Author Approval feature listed below. |
| VS-5758, VS-5757, VS-5756, VS-5755, VS-5754 | Prevent Author Approval in Jira. Administrators now have the ability to prevent record authors from approving a record created from Jira. The author can be defined with a Jira User Picker field or the Route Owner, defined as the user who routed the record for approval. For more information, see "Prevent author approval". |
| VS-5717, VS-5716, VS-5715, VS-5714 |
Custom headers can now be configured for communications from Vera to the target system. For more information, see "Add a custom header to a connection". |
| VS-5724, VS-5723, VS-5722, VS-5721, VS-5719 |
PFX certificates can now be included on a Vera connection to send a certificate for communications between Vera and the target system. For more information, see "Add a client certificate to a connection". |
| VS-5712, VS-5711 | Users designated as the author of a Jira issue will receive notifications when the record they authored is Approved or Rejected. |
Docker image information
| Repositories |
|
| Tags |
|
|
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 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-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. |
| VS-5851 | Rich text from Xray does not format correctly in Vera | Some rich text data from Jira may be displayed incorrectly in Vera due to the way the data is passed from Jira's API and then processed by Vera. This mostly presents as incorrectly displayed formats like bold text, strikethrough text, italicized text, etc. |
| VS-5909 | Vera does not allow for creation of multiple Xray connections | Vera prevents using the same server URL for multiple connections. This causes an issue when trying to set up two different Jira Cloud Xray instances as the server URL for Xray connections will always be the same. |