Vera 2023.2
Software version: Vera 2023.2
Scheduled release date: 27 July 2023
This file provides information about Vera 2023.2:
Version Information
Resolved Issues
New Features
Docker Image Information
Known Issues and Limitations
Version Information
High-level Vera Version | 2023.2 |
|---|---|
Software Build (Can be verified on the "Versions" screen in the web portal.) | Web Portal: 1679 API Server: 4577 (2023/07/27) |
Resolved Issues
Key | Summary | Notes |
|---|---|---|
VS-758 | Folders names are hard coded in the Web Portal | Created new environment variables: VERA_WEB_LOG_DIR (Logs directory), VERA_WEB_CONFIG_DIR (Configs directory), VERA_WEB_CERT_DIR (Certificates Directory) for each directory that was hard coded. |
VS-1243 | Invalid Approval Group error log should indicate what group or line number the error is on | Approval group info is added to the error log when invalid approval group found. |
VS-1613 | Jira Cloud App doesn't display error codes as expected | Fixed an issue where the Vera web panel would not display an error code when the Vera status did not align with the Jira status. |
VS-1918 | Filtering with a # sign causes a 500 error when filtering from the domains table. | Fixed an issue where filtering on the domains table with special characters resulted in an error. |
VS-2116 | The Approval Queue does not unescape record names | Fixed an issue where record names in the Approval Queue did not display special characters correctly. |
VS-2123 | Some special characters don’t work in Record Name search on Record page | Added sanitization for the Records Name field to support records search using special characters. |
VS-2721 | HTML Sanitization for qTest/VERA | The user can see qTest entities with the same formatting on the VERA web portal. |
VS-2979 | Vera Cannot Route a Record when Revision Number contains whitespace character(s) | Fixed an issue where whitespace characters in the Revision Number field caused an error when performing Vera actions. Revision Number will display the appropriate value based on the Vera record. |
VS-3027 | Watermark is misaligned on printed record | Fixed the watermark in the Print View to be center aligned. |
VS-3102 | Toast message for task approval needs to be updated | Changed message from “Task have been approved” to “Task has been approved” when a user approves a single task. |
VS-3328 | Rejection is automatically triggered when clicking an approval task | Fixed an issue where the rejection modal was automatically loaded if a user rejected one task and then selected a new task in the Approval Queue |
VS-3561 | Vera does not refresh qTest API Token appropriately when an error is received from qTest | The qTest Module can now handle invalid_token error. It can refresh the token when it gets this error. This fix prevents the need to restart Vera. |
VS-3562 | Vera does not handle case-insenstive URL matches with sync policy | Fixed an issue where Vera could not connect when the Tosca Workspace URL and Vera Synchronization URL if the URLs did not contain the same case for each character. |
VS-3806 | Task approval/rejection errors when Domain name contains special characters | Fixed issues where approving and rejecting a task could fail if the associated domain contained special characters |
VS-3820 | IDP users can't use approve pencil after approving a record | Fixed an issue where IDP users could not use the approve “pencil” icon on multiple records in a row |
VS-3830 | Vera is not displaying qTest Parameter values for Test Runs | Fixed an issue where the Description and Expected Results from a run with parameters were not displaying the selected parameter value properly. |
VS-3957 | Attachments not showing hyperlinks in Print View | Fixed issue that was not displaying links for non image files. |
VS-3971 | Bulk Approval modal for two different roles should show as single approval | Fixed the approval modal to show the correct number of selected records. |
VS-370, VS-3263, VS-3978, VS-3710, VS-3724 | Security Improvements | Various Security Improvements |
New Features
Key | Summary |
|---|---|
VS-214, VS-2264, VS-2265, VS-3345, VS-3457, VS-3480, VS-3492, VS-3494, VS-3532, VS-3614 | Create and manage multiple policy files in the Vera Web Portal See https://tx3.atlassian.net/wiki/spaces/V20232/pages/306544725 for more information |
VS-3350 | Administrators can manage default policies See https://tx3.atlassian.net/wiki/spaces/V20232/pages/298128819 for more information |
VS-1075, VS-2209, VS-2215, VS-2216, VS-3294, VS-3512, VS-3513, VS-3516, VS-3517, VS-3523, VS-3524, VS-3525, VS-3526, VS-3527, VS-3528, VS-3529, VS-3530, VS-3531, VS-3533, VS-3534, VS-3535, VS-3536, VS-3537, VS-3538, VS-3539, VS-3586, VS-3587, VS-3591 | Create and manage policy sets with customized policy files and domain association See https://tx3.atlassian.net/wiki/spaces/V20232/pages/298128869 for more information |
VS-2776, VS-2777, VS-2778, VS-2779, VS-2782, VS-2895, VS-2896, VS-2929, VS-3370, VS-3390, VS-3411, VS-3421, VS-3428, VS-3466, VS-3467, VS-3473, VS-3474, VS-3500, VS-3514, VS-3541, VS-3558, VS-3590, VS-3666 | Configure, Manage and Test Vera Connection to Source Applications See for more information |
VS-2280, VS-2281, VS-3733, VS-3734 | Record Details and Print View are loaded on demand |
VS-3243, VS-3244 | Enhanced Queuing and Scalability for qTest through Microservices |
VS-3648, VS-3649, VS-3650, VS-3651, VS-3657, VS-3675, VS-3821 | Role Management with Domain Policy Sets and Default Policies |
VS-3035 | Format Tosca Records in Vera |
VS-3412, VS-3413, VS-3415, VS-3416 | Allow Configuration of Vera to Prevent Startup and Verification Activities on Secondary Nodes |
VS-3658 | Remove policies and versions from the Versions page Vera now supports multiple policy files. See for more information |
VS-3875 | Update Requests to qTest to prevent hitting API rate limit |
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-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-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-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-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-3960 | Defect Link is not present in Vera for qTest records | For qTest records, the name of the defect under the defects section is displayed as plaintext rather than a link to the defect. Note: The defect can be navigated to by opening the defects modal and clicking the link on the defect name. |
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. |
VS-4004 | Users are not returned to login page after session timeout | When a user's session expires, they are not redirected to the login page. They will remain on the current page until they attempt to navigate to another page, which will result in an error. |