Vera 2024.1.6
- Jason Koelle
Software version: Vera 2024.1.6
Scheduled release date: 23 December 2024
This file provides information about Vera 2024.1.6:
Version Information
High-level Vera Version | 2024.1.6 |
|---|---|
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 2989 (2024/11/06) API Server: 1.11.1.3 (2024/11/01) |
Resolved Issues
Key | Summary | Notes |
|---|---|---|
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" |
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: Connection Strings |
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-4896 | Projects drop down search cannot handle special characters | On the Records page, searching with special characters in the projects field may result in an error. |
VS-4897 | In the profile page updating email address with invalid email allows to save | User email addresses can be updated and saved with invalid characters. An error message is displayed but the save is done successfully. |
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. |