JIRA-CLD 1.3
Software version: JIRA-CLD 1.3
Publication date:
This file provides information about the VERA Web Portal
- Resolved Issues
- New Features
- Known Issues and Limitations
Resolved Issues
| Key | Summary | Notes |
|---|---|---|
| VS-1030 | VERA Jira Cloud App does not load data on New Issue View | Fixed an issue where the VERA Panel was not displayed consistently in the "New View" in Jira Cloud. Now the panel will only be displayed if the user clicks the Tx3 VERA "quick-add" button or if the status is Routing for Approval, Approved or Rejected. |
| VS-1231 | Jira Cloud clears app settings when app is updated | Previously, the VERA app was storing all customer settings–Atlassian installation settings and VERA configuration settings–together in the same collection of the database. This was causing the VERA settings to become lost every time the Atlassian framework overwrote its installation settings (during registration and re-registration). The two types of settings are now stored in separate collection. |
| VS-1264 | VERA does not recognize duplicate webhook requests from Jira Cloud | Fixed an issue where the Jira module would not recognize duplicate webhooks from Jira Cloud. |
New Features
| Key | Summary |
|---|---|
| VS-1234 | Updated authentication in Atlassian Connect installation hooks |
Known Issues and Limitations
| Key | Summary | Known Issue Details |
|---|---|---|
| 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. |