API 1.5
Software version: API 1.5
Publication date: 01 MAY 2020
This file provides information about the VERA API Server
- Resolved Issues
- New Features
- Docker Image Information
- Known Issues and Limitations
Resolved Issues
| Key | Summary | Notes |
|---|---|---|
| VS-599 | VERA REST Adapter: Message retries cause InvalidOperation exception | Rest adapter now creates a new message request with each retry. |
| VS-607 | Error displaying "All" tasks in approval queue with large quantity of tasks | This specific issue was resolved by VF-599. However, there is a functional threshold to the number of tasks that can be loaded at once. |
| VS-610 | Cannot add large number of users to a domain | Created two separate async calls for adding/removing items to/from a list in the mongo adapter and implemented in the domain modules. |
| VS-620 | User Management table does not load asynchronously | Improved performance of the User Management page by adding server-side pagination to the table of users. |
| VS-629 | qTest webhook errors are not recorded in the error log. | Removed try/catch from Post_RouteAction() so that error handling is done by VERA API Server. |
| VS-658 | The 'Users' list does not sort correctly on Name column | Fixed the Users Management table to allow sorting by the Name of the user. |
New Features
| Key | Summary |
|---|---|
| VS-299 | Implement HTTP Caching between Modules |
| VS-494 | Enforce domain permissions in the approval queue |
| VS-583 | Add meaningful error message for end user when approval or rejection fails |
| VS-603 | Add project to domain |
| VS-622 | View a user's domain assignments. |
| VS-642 | Enhance Module Framework to provide API pagination utilities |
| VS-644 | Use Jira project key as a data field |
Docker
| Repository | veraserver20190209075900.azurecr.io/tx3/vera-server |
|---|---|
| Tags |
|
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-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 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. |
| 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. |