Vera 2023.1.1
Superseded by 2023.1.3
Software version: Vera 2023.1
Scheduled release date: 22 Mar 2023
This file provides information about Vera 2023.1.1:
Version Information
High-level Vera Version | 2023.1.1 |
---|---|
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 1436 (2023/03/22) API Server: 3783 (2023/03/21) |
Resolved Issues
Key | Summary | Notes |
---|---|---|
VS-2123 | Some special characters don't work in Record Name search on Record page | Aded sanitization for the Records Name field to support records search using special characters. |
VS-3356 | Add Bulk notifications to notifications module | Added bulk calls for Notifications Module to optimize database usage. |
VS-3376 | Loading complete qTest Issue when approving leads to timeouts and approval failures. | Optimized approvals of qTest items so only the top qTest item is retrieved to check for Tosca fields. |
VS-3392 | Domains module opens new MongoDB connections directly rather than through Vera.Adapters.Mongo | Prevented Domains module from creating its own Mongo Client per Mongo best practices. |
VS-3400 | Print View does not display image attachments if they do not have file extensions | Fixed to consider files as images when they don’t have content-type and extension. |
VS-3402 | Adding Attachments with Records Breakup saves without Record Breakup. | Fixed the importing of attachments to Vera so each attachment does not rebuild the record. |
Docker Image Information
Repository | http://veraserver20190209075900.azurecr.io/tx3/vera-server http://veraserver20190209075900.azurecr.io/tx3/vera-web-portal |
---|---|
Tags |
|
How to Upgrade | See Upgrade the VERA Server Applications for instructions |
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-962 | Approval Queue user filter uses RegEx can match different users | Due to regular expression matching, a record that has been signed by one user may cause another user's approval queue to exclude the record when it should be available. |
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-1918 | Filtering with a # sign causes a 500 error when filtering from the domains table | Special characters may cause an error when attempting to apply a filter to the domains table. |
VS-2123 | Some special characters don't work in Record Name search on Record page | Using special characters in the Record Name search can cause an error when returning the results of the search. |
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. |