Vera 2024.2.2
- Jason Koelle
Software version: Vera 2024.2.2
Scheduled release date: 23 December 2024
This file provides information about Vera 2024.2.2:
Version Information
High-level Vera Version | 2024.2.2 |
|---|---|
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 3000 (2024/12/23) API Server: 1.11.1.3 (2024/11/14) |
Resolved Issues
Key | Summary | Notes |
|---|---|---|
VS-5960 | Version and Build Date are Swapped on Versions Page - Patch 2024.2 | Fixed an issue where Build Version and Build Date were swapped on the Vera Versions page. |
VS-6043 | Vera Records Fail to Route when qTest Users are Missing an Email Address | Fixed an issue where Vera records failed to route if prevent author approval was configured and a qTest user was missing the email property. |
Docker Image Information
Known Issues and Limitations
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-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. For more information about connection strings, check out the MongoDB documentation (opens in new tab). |
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-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. |