Vera 2023.1.5
Software version: Vera 2023.1.5
Scheduled release date: 14 December 2023
This file provides information about Vera 2023.1.5:
Version Information
High-level Vera Version | 2023.1.5 |
|---|---|
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 2017 (2023/12/08) API Server: 3869 (2023/09/27) |
Resolved Issues
Key | Summary | Notes |
|---|---|---|
VS-4566 | Error "r.map is not a function" when adding projects into a domain | Fixed an issue that was preventing the user from adding projects to a domain |
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-447 | User Administrator role can see Signature Verification Failure Report and Re-verify | A User Administrator can access the Signature Verification reporting section of the Administration Portal. This feature should be limited to System Administrators. |
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 DevOps does not apply a default approval route | If a record is routed for approval that does not satisfy any configured route templates, the user will see "VERA is trying to start the approval route" rather than a descriptive error containing the reason why the route was not started. |
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-1065 | A misleading error message is displayed when VERA cannot apply a final approval | VERA will display a misleading error message when it fails to transition a Jira issue in the workflow. The error message displayed to the user will indicate that there is a connectivity problem, even if it's actually a configuration problem. |
VS-1243 | Invalid Approval Group error log should indicate with group or line number the error is on | Currently error log does not display approval group details when invalid approval group is logged. |
VS-1293 | Final approval fails when Jira projects are configured with a Signatures field | VERA will attempt to write the entire approval route to the Jira Signatures field if the field is present in the Jira project. If the approval route contains over 255 characters the Approval will fail since VERA is attempting to write over 255 characters to the field. |
VS-1419 | Routing records for approval - errors in logs | In the users module, when GET /users/{userId} endpoint is being called with a userId different from the request owner's userId, then users module responses with 403 Forbidden status code. |
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-2156 | Domains do not display in approval queue if the name begins with $ | Domains that begin with a special character may not appear in the approval queue. Records for the domain will still be displayed but the domain column will appear as empty. |
VS-2721 | HTML Sanitization for qTest/VERA | Formatting for qTest records do not display as intended in VERA when the user enters the formatting tags in qTest rather than using the text editor icons. It is recommended that users format their text (bold, italicize, etc) by using qTest’s text editor. |
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-3382 | Role members list is not automatically refreshed when a new user is added to a Role | When adding a new user to a Role, the Role members list is not automatically refreshed, requiring the user to click the refresh table button |
VS-3405 | Some special characters don't work in all columns search on Approval Queue page | Filtering may return either an error or all records when attempting to use special characters when searching in the Approval Queue. |
VS-3410 | Some special characters don't work in all columns search on User Management page | Filtering may return either an error or all users when attempting to use special characters when searching in the User Management page. |
VS-3993 | Cannot re-route/withdraw approval for a record that has no domain association | A record that has previously been routed for approval at least one time cannot be re-routed or withdrawn from its current approval without its corresponding project being associated to a domain. |