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

Key	Summary	Notes
VS-146	Some Jira fields types are not supported by the VERA Records Management Policy	The 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 results	Fixed 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

Key	Summary
VS-436	Route an issue for approval from Jira Cloud

Docker

Repository	veraserver20190209075900.azurecr.io/tx3/vera-server
Tags	1.2.0 win-2016-1.2.0 win-2019-1.2.0 linux-1.2.0

Known Issues and Limitations

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