Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Software version: JIRA-SRVR 1.2

Scheduled release date:   

This file provides information about the VERA DevOps app for Jira Server.

  • Resolved Issues
  • New Features
  • Known Issues and Limitations

Resolved Issues

KeySummary
VS-1289Prevent JIRA from calling VERA for JIRA plugin twice per record to avoid requests overlapping which caused an intermittent issue where the wrong approval route displayed on the Jira record.

New Features

N/A


Known Issues and Limitations

KeySummaryKnown Issue Details
VS-139"Pending Tasks" field refreshes too slowly after route withdrawal.The Pending Tasks field in qTest and Jira is not immediately updated when the record is approved or rejected in VERA. The cached values are updated when the user invokes a browser refresh,
VS-170Rejection Reason is displayed when user creates a sub-task for a jira recordThe Rejection Reason displayed in the Jira App will persist when sub-task records are created. The cached rejection reason is removed when the user invokes a browser refresh.
VS-217Jira web panel hangs on issues without a sync ID.The VERA Approval Route progress spinner and the message "Please wait for VERA to load" is displayed when an issue without a VERA Sync ID is selected from the Issues icon in the Jira sidebar.
VS-221Rejection Reason box lingers in the Issues list.The Rejection Reason displayed in the Jira App will persist when other Jira records are selected. The cached rejection reason is removed when the user invokes a browser refresh.
VS-1293Final approval fails when Jira projects are configured with a Signatures fieldThe VERA integration with Jira utilizes Jira Read-Only custom fields. VERA will attempt to write the entire approval route to the Jira Signatures field if the field is present in the Jira project. If the approval route contains over 255 characters the Approval will fail since VERA is attempting to write over 255 characters to the field.

The Signatures field should be removed as a workaround.
  • No labels