|VS-2150||Entering a duplicate domain name results in unexpected behavior||Corrected the error message when user enters domain name that already exists.|
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.
|VS-2125||User Cannot Approve/Reject Record when Author field is populated||Users can approve or reject records when there is no author user match between the integrated system (Jira, qTest) and VERA|
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-2049||Jira Record displays author as Unknown - Author field should not be displayed if unknown on Jira records||Removed author's field when there is no author and system is different from qTest|
|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.|
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-2033||Add Get Domain by Name API call to Domains module||Optimized retrieval of domain by name.|
|VS-1963||Password Policy throws 500 error when user attempts to save with incorrect data type||Handle exceptions due to bad data being passed in for the Password Policy|
XRay attachments are not being attached correctly
|Fix attachments on Xray for Jira records.|
|VS-1911||Jira records attachments are not displaying/downloading from in VERA||This defect only solves the first of the two attachment problems. The first problem, where the download URL was pointing to the source system instead of VERA, was resolved by nulling the URL on the attachment itself during the import of the file from Jira to VERA so that VERA can apply the correct VERA URL at a later time. The second one, accessing files led to a 404 error, is handled in CCR-142.|
|VS-1889||Remove HTTP Client Retries and make Timeouts configurable||Removed HTTP retries from internal HTTP requests.|
Add configurable HTTP timeouts to handle longer running requests.
|VS-1861||Base Record Type element is missing in Uploaded Records Management Policy||Added base record type property to policies module. This was only done on the develop branch because the bug was introduced in the policy management stories.|
|VS-1700||Cannot re-verify failed signatures|
Fixed unexpected error in reverifying failed signatures.
|VS-1696||The test author is duplicated when the author VERA username and email address is the same||Fixed an issue when authors were matched with the same VERA user twice.|
|VS-1691||Delete User from domain when they are deleted from User Management||When deleting a user, user is also being removed from the domains it was assigned.|
Jira Cloud user custom fields shows as null in VERA
|Adopted user fields for Jira cloud.|
Jira service account cannot authenticate against server if it has no roles
The Jira service account used for the Jira App access updated:
- Develop branch 1.12 - Jira Service account can access approval routes with a System Service Account role
|VS-1583||Slash characters in approval group names cause the Routes Module to fail||Fixed support for approval groups containing slash characters in urls.|
|VS-1391||Revision Number is blank in qTest Run Record Details for History entries||Fixed an issue where the Revision Number field was not captured in the first history entry for certain record types.|
|VS-1235||Approval Queue Project filter does not return records based on filter selection||queryParameters.FieldValuesContain repositioned because of Projections. Domain/Project filter in FieldGroupsBuilder removed|