Software version: API 1.11.3
Publication date: 22 29-JUN-2022
This file provides information about the VERA API Server:
...
| High-level VERA Version | 2022.1.3 |
|---|---|
| API Version | API 1.11.3 |
Software Build (Can be verified on the "Versions" screen in the web portal.) | 27172774 (2022/06/2229) |
Fixed Issues
| Key | Summary | Notes |
|---|---|---|
| VS-1235 | Approval Queue Project filter does not return records based on filter selection | Fixed filtering by Project in the Approval Queue. |
| VS-2033 | Add Get Domain by Name API call to Domains module | Optimized retrieval of domain by name. |
| VS-2034 | Add Jira Webhook Call tracking to allow more retries from Jira | Added handling of Jira Webhook Retries so that VERA will handle retries that had previously not been received. |
| VS-2039 | Create a single static MongoClient to be used in the VERA instance | Use a single instance of the MongoDB driver according to best practices. |
| VS-2073 | VERA always tries to authenticate with the SMTP server even when credentials are not present | Fixed an issue where VERA would try to authenticate against the SMTP server even if it didn't allow for authentication. Now leaving the username and password fields blank will cause VERA to skip the authentication against the SMTP server. |
| VS-2091 | Author sees the issue he routed in the approval queue when author exclusion is enabled | Fixed bug when Prevent Author Approval is set to true in the approval policy JSON but Author value is set to null in the RMP, then author still sees the task in the approval queue. |
| VS-2146 | VERA confuses qTest Test Runs and Test Cases with matching projectId and artifactId pairs. | Fixed record corruption issue when a qTest Test Case and a qTest Test Run have the same qTest artifactId. |
...
| Repository | veraserver20190209075900.azurecr.io/tx3/vera-server |
|---|---|
| Tags |
|
| How to Upgrade | See Upgrade the VERA Server Applications for instructions |
Known Issues and Limitations
See API 1.11