Vera 2023.4
Software version: Vera 2023.4
Scheduled release date: 15 December 2023
This file provides information about Vera 2023.4:
Version Information
High-level Vera Version | 2023.4 |
|---|---|
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 (2023/12/15) |
Resolved Issues
Key | Summary | Notes |
|---|---|---|
VS-4290 | Error message should be shown when Jira can't find route template | Fixed an issue where error messages was not defined for some message keys. |
VS-4295 | Remove User Administrator from user import | User Administrator role is deprecated and removed from CSV user import |
VS-4303 | Test Connection for Xray Cloud always displays success message, even when the test is unsuccessful | Fixed an issue where a test connection for Xray Cloud always displays success message even when the test is unsuccessful. |
VS-4305 | Record Type dropdown on Record Search table includes Sub Type Records | Fixed an issue where users could filter by sub-record types (e.g. Test Steps) on the Records search page. |
VS-4320 | Errors for User Import are off by one | Row numbers were getting mixed after removing blank and duplicate lines in the CSV file. Made an improvement to show the correct row number to the user in error messages. |
VS-4350 | Field validation for certain connections is not correct | Fixed an issue where the field validation for a connection wasn't always correct. |
VS-4358 | HTML styling in Xray distorts the details of the record | Fixed an issue regarding HTML content from Xray that was breaking the page. |
VS-4363 | Timestamp for Draft revisions shows invalid date and time | Fixed an issue that was displaying an incorrect date for draft records |
VS-4399 | When Complete Approval task fails, task status in qTest is incorrectly marked Complete | Fixed an issue where, under certain circumstances, some qTest Tosca Test records would show Complete for a task that failed during approval. |
VS-4400 | Password Policy Settings toast message should not display 400 message | Fixed the password policy page to display the correct validation message when saving the password policy. |
VS-4401 | Mail Server Settings field validation should work independently | Fixed an issue on Mail Server settings that was validating fields that were not edited. |
VS-4406 | Approval panel and Approve/Reject actions that should not be displayed is displaying for the user | Fixed the record details page to not display the approve/reject footer if the user has already approved a task in another level |
VS-4479 | Validation errors are missing for some fields | Fixed an issue on the Connection Details Page that was not displaying the validation messages for the API URL and Browser URL. |
VS-4493 | Vera.Worker microservices are not honoring configurable HTTP timeouts | Enabled the configurable HTTP timeouts in the Vera.Worker microservices. |
VS-4509 | SSO Users with Domain Administrator role cannot edit Domain | Fixed an issue where SAML users with the Domain Administrator role could not access Domain Management. |
VS-4546 | Author can't approve qTest record when Prevent Author Exclusion is set to false on approval route | Fixed an issue prevent an author from approving a record when author exclusion is disabled for a route. |
VS-4425, VS-4567, VS-4573, VS-4574, VS-4575, VS-4594 | Security Improvements | Various Security Improvements |
New Features
Key | Summary |
|---|---|
VS-2665, VS-2666, VS-3002, VS-4434, VS-4435, VS-4438, VS-4439, VS-4440, VS-4458, VS-4459, VS-4460, VS-4461, VS-4521 | User Profile Email Notification Settings: Users can now configure whether or not they would like to receive email notifications. Users can disable all email notifications or can opt in to emails for specific domains. See https://tx3.atlassian.net/wiki/spaces/V20234/pages/526385153 for more information. |
VS-2814, VS-4430, VS-4431, VS-4432, VS-4433, VS-4619 | User Profile Audit Logs: System Administrators are now able to view audit history of user profiles. See https://tx3.atlassian.net/wiki/spaces/V20234/pages/495321103 for more information. |
VS-4442, VS-4443, VS-4444, VS-4446, VS-4447 | GainsightPX Integration: Gainsight PX is a product experience platform that enables product teams to understand how users use their products, collect feedback, and create in-app engagements like product walkthroughs to drive user onboarding and product adoption. When customers log into the Vera Web Portal and Gainsight is enabled, anonymous information about how they use and navigate through the Web Portal is collected and stored in Gainsight. |
VS-4424, VS-4452, VS-4529 | Concurrent Usage Reports: System Administrators can now view and export a report showing the number of concurrent users in Vera over a customizable time period. See https://tx3.atlassian.net/wiki/spaces/V20234/pages/496435259 for more information. |
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: |
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. |