API 1.2

Software version: API 1.2

Publication date: 08 NOV 2019

This file provides information about the VERA 3 API Server

  • Resolved Issues
  • New Features
  • Docker Image Information
  • Known Issues and Limitations

Resolved Issues

VS-146Some Jira fields types are not supported by the VERA Records Management PolicyThe Jira Any and Components data types can be included in VERA records as data fields.
VS-456"View Last Import" results button does not display page with import resultsFixed an issue on the server in which the location of the stored results file of the "Import Users" feature could not be found on a Linux-based system.

New Features

VS-436Route an issue for approval from Jira Cloud


  • 1.2.0
  • win-2016-1.2.0
  • win-2019-1.2.0
  • linux-1.2.0

Known Issues and Limitations



Known Issue Details

VS-501Jira Module only uses the first Jira credentials found in the Synchronization PolicyAn 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. 
VS-383Tester(s) not included in Execution Log in VERAqTest Tester name is not displayed in VERA web portal.  The VERA Record Management Policy can be updated to include the Tester field in VERA.


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.


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.