API 1.9.2
Software version: API 1.9.2
Scheduled release date:
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-344 | Enforce a minimum password complexity | Enforce a minimum password complexity level when a user is changing their password |
| VS-1142 | Special character in group name is preventing the role membership table from displaying users | Resolved an issue where a special character (e.g. forward slash) was causing the Role Membership table to not be displayed properly |
| VS-1181 | Activity History does not show details of Linked Record | Resolved viewing details of a record's activity history in Jira |
| VS-1264 | VERA does not recognize duplicate webhook requests from Jira Cloud | Resolved an issue where the Jira module would not recognize duplicate webhooks from Jira Cloud |
| VS-1290 | vera-server-info logs are not sensitive to logging levels | Logging is now binded to the “VERA_SERVER_LOG_LEVEL” environment variable |
| VS-1300 | SMTP Module will attempt to use SSL even if the StartTLS button is not checked | Notifications module now properly handles "useTls" option |
| VS-1306 | Add support for inconsistent Xray Test Run Evidence JSON representation | Updated the VERA API to support parsing an unexpected format of Xray Test Execution data as observed in a customer environment |
| VS-1312 | Change the sender for notifications to only be the configured admin email address | Resolved an issue where VERA would attempt to send an email from a user with domain that was trusted by our email provider. Now VERA will only use the configured From email address in the From field and will use the user's email address in the Reply To field |
New Features
| N/A | N/A |
|---|
Docker
| Repository | veraserver20190209075900.azurecr.io/tx3/vera-server |
|---|---|
| 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-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-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. |
| VS-810 | Admin can't remove a project from domain if project name contains regex | A project created with regex characters cannot be removed from a domain once it is added. This also causes issues with displaying tasks in the approval queue for a user |
| 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-1060 | If user has a null value for a role in their claims list the user module fails to add or remove them from a role | If a user has a claim that has a type of role and a value of null (not just a blank string), the user module will throw an exception when trying to add or remove the user from a role. |
| 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-1095 | Project names are not validated when adding to domain | Admins are able to add a project to a domain that contains RegEx characters. |
| 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-1262 | Routing Test Execution for Approval fails if test has Xray custom test step fields | When routing a Test Execution if will fail if test has any of these custom test step fields.
|
| VS-1263 | VERA does not properly handle a hidden Sync ID field in Jira | VERA does not have valid error handling for scenarios in which the VERA Sync ID field in Jira is inaccessible (e.g.. not on the issue's edit screen). |
| VS-1277 | VERA returns an HTTP 500 status code to Jira webhooks when it cannot access the Sync ID field | With Jira Cloud, the HTTP 500 status code will prompt Jira to retry the same webhook a few minutes later. This is undesirable, because a) there is no reasonable expectation that it will succeed, and b) the user will have very likely tried rerouting the record again anyway. Therefore, the Jira module should return a different status code that will not trigger a retry from Jira Cloud. |
| VS-1278 | VERA does not handle concurrent start route requests for the same record | The VERA API does not have proper handling for concurrent start approval route requests for the same record. If it is a new record, then the end result could be the record receiving two different Sync IDs each with its own approval route. |
| VS-1280 | VERA does not clean-up routes on Start Route, Revise, Approve, etc. | The VERA/Jira API will proactively clean-up the routes associated with a record by cancelling all routes when one of them is cancelled. This clean-up should occur on other triggers as well, because there should never be more than one "active" route for a record at a time. |
| 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. |