Software version: API 1.0
Publication date: 19 JUL 2019
This file provides information about the VERA 3 Application Server
- Resolved Issues
- Known Issues and Limitations
Known Issues and Limitations
known issue details
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.
qTest Test Case Version is set to 2 instead of 1 on initial approval
There is an intermittent issue were a qTest Test Case version is incremented two major versions instead of one when a qTest Test Case is pre-execution approved with VERA. For example, the qTest Test Case is routed for approval and the qTest Version is 0.7 The qTest Test Case is approved in VERA and should update the qTest Test Case Version field to 1.0 instead the Version field is updated to 2.0
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.
Some Jira fields types are not supported by the RMP
VERA can include the following Jira data types when creating a Jira record in VERA; basic arrays, string, issuetype, priority, project, user, option, and number. VERA. VERA cannot include fields that are Jira data types of any, components or issuelink,