...
Key | Summary | Known 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-170 | Rejection Reason is displayed when user creates a sub-task for a jira record | The 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-217 | Jira 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-221 | Rejection 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-1293 | Final approval fails when Jira projects are configured with a Signatures field | The 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.