Software version: API 1.6.1
Publication date: 18 NOV 2020
This file provides information about the VERA API Server
- Resolved Issues
- New Features
- Docker Image Information
- Known Issues and Limitations
|VS-930||First cancelled route is displayed in qTest for any cancelled route||Fixed an issue where qTest records that had been cancelled multiple times always showed the first cancelled approval route in qTest.|
Update Approval Queue with Domain Name, Location ID and Project
|Updated the displayed columns in the approval queue to align with domain-driven organization of VERA.|
Known Issues and Limitations
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-323||VERA Server needs a reboot to fully read new Sync Policy entries||Changes to the VERA Synchronization Policy will not take affect until the VERA Application service is restarted.|
|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-512||Jira Cloud Readonly Fields are Editable in New View|
An issue exists in Jira Cloud in which "Readonly" fields are actually editable in Jira Cloud's "New View". This issue impacts theÂ VERA Sync IDÂ andÂ VERA Pending TasksÂ fields. Users should be careful to not edit these fields.
Editing the VERA Sync ID field will break the issue's synchronization with VERA, and unintentional changes should be reverted.
Editing the Pending Tasks field will break any user-defined Jira filters for pending approval tasks. Changes can be reverted manually, or the field will update automatically the next time an approval action occurs.
Reference Atlassian Issue ID JRACLOUD-72479:Â https://jira.atlassian.com/browse/JRACLOUD-72479
|VS-606||Error while sorting approval queue with large quantity of tasks||Users may encounter errors while sorting an approval queue with a large (thousands) quantity of tasks.|
|VS-668||Sorting shows all values beginning with a capital letter before lowercase values||When sorting data (users, records, etc.) alphabetically, the system erroneously alphabetizes capital letters independently from lower-case letters. For example: Apple, Cat, ball -- instead of: Apple, ball, Cat|
|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.|