Vera 2023.1
Superseded by Vera 2023.1.4
Software version: Vera 2023.1
Scheduled release date: 17 Feb 2023
This file provides information about Vera 2023.1:
Version Information
Resolved Issues
New Features
Docker Image Information
Known Issues and Limitations
Version Information
High-level Vera Version | 2023.1 |
---|---|
Versions | WP 1.14 API 1.14 |
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 1379 API Server: 3730 (2023/02/14) |
Resolved Issues
Key | Summary | Notes |
---|---|---|
VS-163 | Rejection Reason can be submitted with only a space (no text) entered | Whenever user tries to add text with only whitespaces or whitespace at the start or at the end, this space will be removed when the user leaves the field. |
VS-692 | JSON Attachment download returns 500 error | Fixed issue where a JSON Attachment download returns 500 error. |
VS-859 | An admin cannot blank a user's email address | Fixed an issue that was not showing validation error message for each field when the user leaves the field or when the form is submitted. |
VS-962 | Approval Queue user filter uses RegEx can match different users | Fixed issue where approval queue filter would incorrectly match users by removing all RegEx in VS-2042 |
VS-1584 | A matching location could not be found error when Jira or qTest URL in sync policy contains forward slash | Fixed an issue where a trailing slash in the Synchronization Policy's Server URL would cause an error when performing VERA transitions in Jira and qTest. |
VS-1936 | Refresh Table button on the Policy Management table doesn't refresh the table | Fixed the component to fetch data when the user clicks on the refresh button. |
VS-2042 | Remove RegEx from Mongo field match queries | Optimized database queries so that equality comparisons do not use regular expressions to allow for the use of indexes. |
VS-2062 | Mail setting's test email form info does not persist | Fixed Send Test Email Modal to not clear the data after closing the modal. |
VS-2181 | Cancelling Admin login returns the user to a broken Approval Queue | Fixed behavior of the cancel button on Admin Login Page to return to the previous page instead crashing the screen. |
VS-2189 | SAML login errors don't cause a toast popup in React web portal | Fixed the error message of SAML Login to show the correct username |
VS-2205 | No Error Message when unauthorized user attempts to access Domain Management | Added a toast message with the text “You don't have access to this page” when the user attempts to access an unauthorized page by changing the URL on the address bar or through a direct link. |
VS-2233 | Domain can be submitted with only a space for Name | Whenever user tries to add text with only whitespaces or whitespace at the start or at the end, this space will be removed after the user leaves the field. |
VS-2239 | Add user input fields provides incorrect feedback | Fixed validation on Add User Page. It will now display the validation when the user leaves a field with invalid input or when the user tries to save the changes with invalid inputs. |
VS-2247 | When a Jira Approval fails on the transition, VERA does not reset Jira fields | Fixed an issue where Signatures and Pending Tasks fields would update in Jira when a VERA signature failed. |
VS-2302 | qTest Run Table Columns do not line up when information is missing | Fixed an issue where empty field values for qTest Run Steps (or any empty fields in linked records) were not displayed in the Vera web portal. |
VS-2339 | Signature usernames do not appear correctly on the Print View for previously approved revisions | Fixed an issue where a user’s ID would appear in the approval table for previous revisions of a record in the Print View. |
VS-2642 | Web portal doesn't redirect to login page when session expires | Fixed the session behavior so that when a user's session expires, the web portal sends the user to a login page. |
VS-2711 | qTest Step attachments download as zip files | Fixed an issue where attachments at the step level of a qTest record would be downloaded as a zip file with a generic name. |
VS-2774 | Previous Revisions do not show the proper domain for the record | Fixed an issue that was not showing domain name on any previous record's revision. |
VS-2829 | Route Tab is not appearing on the record details | Fixed an issue that was hiding the Approval Routes tab on the record details page. |
VS-2845 | qTest does not refresh auth token after expiration | Refreshes qTest token if qTest responds with a 401 (Unauthorized) to any request. |
VS-2846 | Reviewer name is not displayed on web portal | Fixed an issue where the VERA signature ID was displaying in the Reviewer field rather than the reviewer’s name in some scenarios |
VS-2870 | Role Membership appears empty under certain conditions | Fixed Role Management Page to show users after selecting a new role. |
VS-2872 | User with multiple roles approves a task and still sees approve/reject buttons bar | Fixed the condition that verifies if the user is allowed to see approval buttons. Now if the user has already approved a task in any role, they won't be allowed to see the approval buttons again, even if they have another role. |
VS-2898 | Blank page when backspace is pressed on Domain Owner Field on Create Domain Modal | Fixed the domain owner field on Create Domain Modal that was causing the backspace key to redirect the user to a blank page |
VS-2930 | VERA Bulk Approval progress modal displays failure and timeout but approvals succeed | Fixed bulk approval requests to run in background instead of displaying a progress window that incorrectly shows a failure message. |
VS-2931 | Approval-Queue row selection dropdown returns to default after selection other value | Fixed row selection to display the previously selected option. |
VS-2955 | Errors are showing invalid requests to signatures API | Fixed invalid request that was being dispatched using the username instead of the user’s id. |
VS-3110 | Name Field does not wrap | Fixed an issue where the Name field would overflow into other field columns by wrapping the text and limiting it to 5 lines |
VS-3149 | After clicking in a Linked Record Arrow Icon, all Linked Records with the same name are expanded or collapsed | Fixed an issue where linked record sections would expand/collapse all sections with the same name. |
New Features
Key | Summary |
---|---|
VS-1158, VS-1159, VS-1160, VS-1161, VS-1162, VS-1163, VS-2646, VS-3033, VS-3035, VS-3041, VS-3053 | Route a Tosca Test Case for Pre-Execution Approval in qTest |
VS-1164, VS-1165, VS-1166 | Withdraw or Reject Approval Route / Task associated to Tosca Test Case in qTest |
VS-3026 | Complete Tosca Test Case Pre-execution Approval in Tosca |
VS-1167, VS-1168 | Revise Approved Tosca Test Case in qTest |
VS-1147, VS-1149, VS-1150 | Route a Tosca Execution for Approval in qTest |
VS-2359, VS-2360 | View Tosca Execution List Details and Attachments in Vera |
VS-1984 | Capture qTest Custom Test Step Fields in VERA |
VS-2269, VS-2272, VS-2273, VS-2274, VS-2275 | Reworked how records are stored to prevent hitting the maximum document size for a MongoDB document. |
VS-2354, VS-2355, VS-2399, VS-2400, VS-2762 | View and Approve X-Ray Cloud Test Cases in Vera |
VS-2356, VS-2357, VS-2640, VS-2641, VS-2654 | View and Approve X-Ray Cloud Test Executions / Sub Executions in Vera |
VS-2742 | Admin can View User Roles in Domain Details |
Docker Image Information
Repository | |
---|---|
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. |