Vera 2023.4.1
- Jason Koelle
Software version: Vera 2023.4.1
Scheduled release date: 27 March 2024
This file provides information about Vera 2023.4.1:
Version Information
High-level Vera Version | 2023.4.1 |
|---|---|
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 2047 (2023/12/15) API Server: 1.10.1.0 (2024/03/27) |
Resolved Issues
Key | Summary | Notes |
|---|---|---|
VS-4915 | Approval Queue displays tasks outside of user role when domain column is filtered with ")" | Fixed an issue where users could see tasks outside of their role in the approval queue when using parentheses within a search filter. |
New Features
Key | Summary |
|---|---|
Add User Agent to Jira Client Connections | Add User Agent to Jira Client Connections |
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" |
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. See link for more details: https://www.mongodb.com/docs/manual/reference/connection-string/ |
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-4297 | Defect modal displays full url for defect, not text of defect name | Defects modal will display the full link to a defect rather than the defect name as a hyperlink. |
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-4623 | Filtering connections columns with special characters gives a 500 error | Admins cannot filter with certain special characters in the Connections table. |