...
| Key | Summary |
|---|---|
| VS-8 | View VERA version information in VERA web portal |
| VS-77 | Reject a Record Directly from the Approval Queue (Preview Feature Only) |
| VS-529 | Implement an INFO logging level |
| VS-530 | Implement a FULL logging level |
| VS-537 | Implement a NONE logging level |
| VS-565 | Improve loading of the approval queue when it loads (Preview Feature Only) |
| VS-591 | Admin can view domain details (Preview Feature Only) |
| VS-592 | An admin can add user(s) to a domain (Preview Feature Only) |
| VS-593 | An admin can remove user(s) from a domain (Preview Feature Only) |
| VS-605 | Admin can delete domain (Preview Feature Only) |
| --- | Misc. enhancements to improve software security |
| --- | Misc. enhancements to the VERA REST API |
Docker
| Repository | veraserver20190209075900.azurecr.io/tx3/vera-server |
|---|---|
| Tags |
|
Known Issues and Limitations
Key | Summary | Known Issue Details | ||
|---|---|---|---|---|
| VS-501 | Jira Module only uses the first Jira credentials found in the Synchronization Policy | An issue exists when multiple Jira instances are configured in the Synchronization Policy. The Jira module will select the first record location with the Jira system label and not the matching location from the webhook. 629 | qTest webhook errors are not recorded in the error log. | If a qTest callback action results in a HTTP 500 status code, the error will not be recorded in the VERA API Server error log. |
| VS-610 | Cannot add large number of users to a domain at once | (Preview Feature Only) Admins are not able to add more than 999 users to a VERA domain in a single operation. | ||
| VS-383 | Tester(s) not included in Execution Log in VERA | qTest Tester name is not displayed in VERA web portal. The VERA Record Management Policy can be updated to include the Tester field in VERA. | ||
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-222 | Tasks show Not Started instead of Cancelled after rejection | Approval Tasks are set to Not Started when an approval task in the same approval route is Rejected. The approval tasks should be set to Cancelled when an approval task in the same approval route is Rejected. |
...