Whereas it was possible for a migration to hang indefinitely, this release ensures that the server-to-cloud transfer is always settled; that is, a result is always reported in the JCMA user interface on the server side.
Version history
CloudJira Cloud2024-02-15Improved robustness for server-to-cloud migrations via JCMA 6.2.23Jira Data Center 8.0.0 - 9.15.12024-04-20(Jira 8,9) Bug fixes - [FIXED] Very long issue keys are truncated on the risk table. This fix allows the table to adjust column widths to accommodate issue keys.
- [FIXED] Dashboard gadgets don't display when the app license is invalid. This fix removes that restriction.
6.2.23Jira Server 8.0.0 - 9.15.12024-04-20(Jira 8,9) Bug fixes - [FIXED] Very long issue keys are truncated on the risk table. This fix allows the table to adjust column widths to accommodate issue keys.
- [FIXED] Dashboard gadgets don't display when the app license is invalid. This fix removes that restriction.
6.2.22Jira Data Center 8.0.0 - 9.15.12024-03-28(Jira 8,9) Cloud migration bug fix [FIXED] Jira Cloud Migration Assistant creates duplicate custom fields when the administrator chooses the "Migrate all data at once" option.
6.2.22Jira Server 8.0.0 - 9.15.12024-03-28(Jira 8,9) Cloud migration bug fix [FIXED] Jira Cloud Migration Assistant creates duplicate custom fields when the administrator chooses the "Migrate all data at once" option.
6.2.21Jira Data Center 8.0.0 - 9.14.12024-01-15(Jira 8,9) Security patch - [FIXED] Updated dependencies to remove exposure to security vulnerabilities in the related software libraries.
6.2.21Jira Server 8.0.0 - 9.14.12024-01-15(Jira 8,9) Security patch - [FIXED] Updated dependencies to remove exposure to security vulnerabilities in the related software libraries.
6.2.21-j7Jira Data Center 7.2.0 - 7.13.182024-01-15(Jira 7.x) Security patch Version 6.2.21-j7 • Released 2024-01-15 • Supported By ProjectBalm • Paid via Atlassian • Commercial- [FIXED] Updated dependencies to remove exposure to security vulnerabilities in the related software libraries.
6.2.21-j7Jira Server 7.2.0 - 7.13.182024-01-15(Jira 7.x) Security patch Version 6.2.21-j7 • Released 2024-01-15 • Supported By ProjectBalm • Paid via Atlassian • Commercial- [FIXED] Updated dependencies to remove exposure to security vulnerabilities in the related software libraries.
6.2.20Jira Data Center 8.0.0 - 9.12.72023-09-26(Jira 8,9) No change This release simply ensures version number parity with the latest update to the Jira 7.x edition of the app.
6.2.20Jira Server 8.0.0 - 9.12.72023-09-26(Jira 8,9) No change This release simply ensures version number parity with the latest update to the Jira 7.x edition of the app.
6.2.19-j7Jira Data Center 7.2.0 - 7.13.182023-08-04(Jira 7.x) Bug fix Version 6.2.19-j7 • Released 2023-08-04 • Supported By ProjectBalm • Paid via Atlassian • CommercialThis release fixes a bug that prevented the App Settings, Risk Models, and Risk Registers pages in the Administration area from being displayed in Jira 7.
6.2.19-j7Jira Server 7.2.0 - 7.13.182023-08-04(Jira 7.x) Bug fix Version 6.2.19-j7 • Released 2023-08-04 • Supported By ProjectBalm • Paid via Atlassian • CommercialThis release fixes a bug that prevented the App Settings, Risk Models, and Risk Registers pages in the Administration area from being displayed in Jira 7.
6.2.18Jira Data Center 8.0.0 - 9.11.32023-06-16(Jira 8,9) Maintenance release This release is to ensure compatibility with ongoing maintenance releases of the server-to-cloud migration library on which this app depends.
6.2.18Jira Server 8.0.0 - 9.11.32023-06-16(Jira 8,9) Maintenance release This release is to ensure compatibility with ongoing maintenance releases of the server-to-cloud migration library on which this app depends.
6.2.18-j7Jira Data Center 7.2.0 - 7.13.182023-06-16(Jira 7.x) Maintenance release Version 6.2.18-j7 • Released 2023-06-16 • Supported By ProjectBalm • Paid via Atlassian • CommercialThis release is to ensure compatibility with ongoing maintenance releases of the server-to-cloud migration library on which this app depends.
6.2.18-j7Jira Server 7.2.0 - 7.13.182023-06-16(Jira 7.x) Maintenance release Version 6.2.18-j7 • Released 2023-06-16 • Supported By ProjectBalm • Paid via Atlassian • CommercialThis release is to ensure compatibility with ongoing maintenance releases of the server-to-cloud migration library on which this app depends.
6.2.17Jira Data Center 8.0.0 - 9.9.22023-06-05(Jira 8,9) Bug fix FIXED: An OSGi bundle dependency issue prevents the app from starting properly.
6.2.17Jira Server 8.0.0 - 9.9.22023-06-05(Jira 8,9) Bug fix FIXED: An OSGi bundle dependency issue prevents the app from starting properly.
6.2.16Jira Data Center 8.0.0 - 9.8.22023-05-30(Jira 8,9) Bug fix FIXED: This release rectifies an error in the deployment of version 6.2.15.
6.2.16Jira Server 8.0.0 - 9.8.22023-05-30(Jira 8,9) Bug fix FIXED: This release rectifies an error in the deployment of version 6.2.15.
6.2.15Jira Data Center 8.0.0 - 9.8.22023-05-30(Jira 8,9) Security assurance, bug fix - FIXED: Remove one medium-severity vulnerability in a dependent code library.
- FIXED: Avoid OSGi module mismatches by explicitly declaring dependency versions for affected packages.
6.2.15Jira Server 8.0.0 - 9.8.22023-05-30(Jira 8,9) Security assurance, bug fix - FIXED: Remove one medium-severity vulnerability in a dependent code library.
- FIXED: Avoid OSGi module mismatches by explicitly declaring dependency versions for affected packages.
6.2.15-j7Jira Data Center 7.2.0 - 7.13.182023-05-30(Jira 7.x) Security assurance, bug fix Version 6.2.15-j7 • Released 2023-05-30 • Supported By ProjectBalm • Paid via Atlassian • Commercial- FIXED: Remove one medium-severity vulnerability in a dependent code library.
- IMPROVED: Replaced product logo images.
- IMPROVED: Other minor optimizations
6.2.15-j7Jira Server 7.2.0 - 7.13.182023-05-30(Jira 7.x) Security assurance, bug fix Version 6.2.15-j7 • Released 2023-05-30 • Supported By ProjectBalm • Paid via Atlassian • Commercial- FIXED: Remove one medium-severity vulnerability in a dependent code library.
- IMPROVED: Replaced product logo images.
- IMPROVED: Other minor optimizations
6.2.14Jira Data Center 8.0.0 - 9.8.22023-04-14(Jira 8,9) Security improvement and bug fix - [FIXED] Missing Contingency plan field reported as missing Residual risk field.
- [IMPROVED] Removed direct dependency on JQuery to avoid potential exposure to any vulnerabilities in that library.
6.2.14Jira Server 8.0.0 - 9.8.22023-04-14(Jira 8,9) Security improvement and bug fix - [FIXED] Missing Contingency plan field reported as missing Residual risk field.
- [IMPROVED] Removed direct dependency on JQuery to avoid potential exposure to any vulnerabilities in that library.
6.2.13Jira Data Center 8.0.0 - 9.7.22023-02-14(Jira 8, 9) Bug fix and performance improvement - [FIXED] Inability to load project-specific risk models that are associated with very many (over roughly 1500) projects.
- [IMPROVED] Reduced time to load the Risk model administration pages.
6.2.13Jira Server 8.0.0 - 9.7.22023-02-14(Jira 8, 9) Bug fix and performance improvement - [FIXED] Inability to load project-specific risk models that are associated with very many (over roughly 1500) projects.
- [IMPROVED] Reduced time to load the Risk model administration pages.
6.2.12Jira Data Center 8.0.0 - 9.6.02022-09-23(Jira 8, 9) Improved risk model editor - [IMPROVED] Introduced a confirmation dialog when changing risk-model-to-project assignments and when deleting risk models.
- [NEW] Added the ability to search for projects to add to the context of a risk model.
6.2.12Jira Server 8.0.0 - 9.6.02022-09-23(Jira 8, 9) Improved risk model editor - [IMPROVED] Introduced a confirmation dialog when changing risk-model-to-project assignments and when deleting risk models.
- [NEW] Added the ability to search for projects to add to the context of a risk model.
6.2.11Jira Data Center 8.0.0 - 9.2.12022-08-19(Jira 8, 9) Risk assessment truncation bug fix This release fixes a bug that causes the risk assessment panel to be truncated when using the latest version of Google Chrome, MS Edge, and other Chromium-based browsers.
6.2.11Jira Server 8.0.0 - 9.2.12022-08-19(Jira 8, 9) Risk assessment truncation bug fix This release fixes a bug that causes the risk assessment panel to be truncated when using the latest version of Google Chrome, MS Edge, and other Chromium-based browsers.
6.2.10Jira Data Center 8.0.0 - 9.1.12022-04-09(Jira 8.x) Updated various internal library dependencies This is a maintenance release in line with our policy of regularly updating library dependencies to their latest versions.
6.2.10Jira Server 8.0.0 - 9.1.12022-04-09(Jira 8.x) Updated various internal library dependencies This is a maintenance release in line with our policy of regularly updating library dependencies to their latest versions.
6.2.9Jira Data Center 8.0.0 - 8.22.62022-04-07(Jira 8.x) Corrected a bug introduced in 6.2.8 This release corrects an error introduced in version 6.2.8, which is no longer available on the Marketplace.
6.2.9Jira Server 8.0.0 - 8.22.62022-04-07(Jira 8.x) Corrected a bug introduced in 6.2.8 This release corrects an error introduced in version 6.2.8, which is no longer available on the Marketplace.
6.2.9-j7Jira Data Center 7.2.0 - 7.13.182023-04-03(Jira 7.x) Enable migration to cloud via JCMA This release fixes a problem that caused migrations to Jira Cloud to stall in 'READY' state.
6.2.9-j7Jira Server 7.2.0 - 7.13.182023-04-03(Jira 7.x) Enable migration to cloud via JCMA This release fixes a problem that caused migrations to Jira Cloud to stall in 'READY' state.
6.2.8-j7Jira Data Center 7.2.0 - 7.13.182022-04-07(Jira 7.x) Removed redundant Spring Framework transitive dependency - [IMPROVED] Removed redundant Spring Framework transitive dependency.
Risk Register is not vulnerable to the exploit reported under the CVE-2022-22965 advisory. The product has no runtime dependency on the vulnerable Spring Framework libraries. Nevertheless, out of an abundance of caution, we are updating any transitive development-time dependency on Spring Framework libraries.
6.2.8-j7Jira Server 7.2.0 - 7.13.182022-04-07(Jira 7.x) Removed redundant Spring Framework transitive dependency - [IMPROVED] Removed redundant Spring Framework transitive dependency.
Risk Register is not vulnerable to the exploit reported under the CVE-2022-22965 advisory. The product has no runtime dependency on the vulnerable Spring Framework libraries. Nevertheless, out of an abundance of caution, we are updating any transitive development-time dependency on Spring Framework libraries.
6.2.7Jira Data Center 8.0.0 - 8.22.62022-03-29(Jira 8.x) Bug fixes, security tightening - [FIXED] Cloud migrations get stuck on 0% progress if no projects are included in the migration.
- [FIXED] Removed one low-severity security vulnerability and one medium-severity security vulnerability.
6.2.7Jira Server 8.0.0 - 8.22.62022-03-29(Jira 8.x) Bug fixes, security tightening - [FIXED] Cloud migrations get stuck on 0% progress if no projects are included in the migration.
- [FIXED] Removed one low-severity security vulnerability and one medium-severity security vulnerability.
6.2.6Jira Data Center 8.0.0 - 8.22.62022-02-19[Jira 8.x] Version bump There is no change in this release except for the version number, which has been updated in order to maintain consistency in the Marketplace listing for this product.
6.2.6Jira Server 8.0.0 - 8.22.62022-02-19[Jira 8.x] Version bump There is no change in this release except for the version number, which has been updated in order to maintain consistency in the Marketplace listing for this product.
6.2.6-j7Jira Data Center 7.2.0 - 7.13.182022-02-14[Jira 7.x] Bug fix [FIXED] Risk model health check fails because of a missing logging component.
6.2.6-j7Jira Server 7.2.0 - 7.13.182022-02-14[Jira 7.x] Bug fix [FIXED] Risk model health check fails because of a missing logging component.
6.2.5Jira Data Center 8.0.0 - 8.22.62022-02-04[Jira 8.x] Fix problem with automated server-to-cloud migrations - [FIXED] Automated cloud migration feature returning errors.
6.2.5Jira Server 8.0.0 - 8.22.62022-02-04[Jira 8.x] Fix problem with automated server-to-cloud migrations - [FIXED] Automated cloud migration feature returning errors.
6.2.4Jira Data Center 8.0.0 - 8.21.12021-12-09(Jira 8.x) Confluence matrix bug fix NOTE: if you are upgrading from version 6.1.6 or earlier of the app, a reboot of Jira may be required after the upgrade. In some Data Center configurations, some node failures during the upgrade process have been reported. Under those circumstances, restarting Jira restores normal functionality with no harm to the app or your data.
- [FIXED] Risk matrix gadget not working when embedded in a Confluence page.
- [FIXED] JVM halted upon upgrade of the app because of a changed OSGi Bundle-SymbolicName.
6.2.4Jira Server 8.0.0 - 8.21.12021-12-09(Jira 8.x) Confluence matrix bug fix NOTE: if you are upgrading from version 6.1.6 or earlier of the app, a reboot of Jira may be required after the upgrade. In some Data Center configurations, some node failures during the upgrade process have been reported. Under those circumstances, restarting Jira restores normal functionality with no harm to the app or your data.
- [FIXED] Risk matrix gadget not working when embedded in a Confluence page.
- [FIXED] JVM halted upon upgrade of the app because of a changed OSGi Bundle-SymbolicName.
6.2.4-j7Jira Data Center 7.2.0 - 7.13.182021-12-10(Jira 7.x) Stability upgrade NOTE: if you are upgrading from version 6.1.6-j7 or earlier of the app, a reboot of Jira may be required after the upgrade. In some Data Center configurations, some node failures during the upgrade process have been reported. Under those circumstances, restarting Jira restores normal functionality with no harm to the app or your data.
- [FIXED] JVM halted upon upgrade of the app because of a changed OSGi Bundle-SymbolicName.
6.2.4-j7Jira Server 7.2.0 - 7.13.182021-12-10(Jira 7.x) Stability upgrade NOTE: if you are upgrading from version 6.1.6-j7 or earlier of the app, a reboot of Jira may be required after the upgrade. In some Data Center configurations, some node failures during the upgrade process have been reported. Under those circumstances, restarting Jira restores normal functionality with no harm to the app or your data.
- [FIXED] JVM halted upon upgrade of the app because of a changed OSGi Bundle-SymbolicName.
6.2.3Jira Data Center 8.0.0 - 8.20.302021-11-19(Jira 8.x) Bug fix - duplicate custom fields This release fixes a problem that caused a new set of custom fields to be created, and previously-created risk registers to disappear from the risk register list.
6.2.3Jira Server 8.0.0 - 8.20.302021-11-19(Jira 8.x) Bug fix - duplicate custom fields This release fixes a problem that caused a new set of custom fields to be created, and previously-created risk registers to disappear from the risk register list.
6.2.3-j7Jira Data Center 7.2.0 - 7.13.182021-11-19(Jira 7.x) Bug fix - duplicate custom fields This release fixes a problem that caused a new set of custom fields to be created, and previously-created risk registers to disappear from the risk register list.
6.2.3-j7Jira Server 7.2.0 - 7.13.182021-11-19(Jira 7.x) Bug fix - duplicate custom fields This release fixes a problem that caused a new set of custom fields to be created, and previously-created risk registers to disappear from the risk register list.
6.1.6Jira Data Center 8.0.0 - 8.20.302021-06-02(Jira 8.x) Bug fix - [FIXED] App settings page endlessly loads itself when the number of screen schemes on the Jira instance is extremely large.
6.1.6Jira Server 8.0.0 - 8.20.302021-06-02(Jira 8.x) Bug fix - [FIXED] App settings page endlessly loads itself when the number of screen schemes on the Jira instance is extremely large.
6.1.6-j7Jira Data Center 7.2.0 - 7.13.182021-06-04(Jira 7.x) Bug fix - [FIXED] App settings page endlessly loads itself when the number of screen schemes on the Jira instance is extremely large.
6.1.6-j7Jira Server 7.2.0 - 7.13.182021-06-04(Jira 7.x) Bug fix - [FIXED] App settings page endlessly loads itself when the number of screen schemes on the Jira instance is extremely large.
6.1.5Jira Data Center 8.0.0 - 8.17.02021-03-31(Jira 8.x) Bug fix - FIXED: As of the previous release, clicking on a cell in the risk matrix gadget fails to open a list of associated risks.
6.1.5Jira Server 8.0.0 - 8.17.02021-03-31(Jira 8.x) Bug fix - FIXED: As of the previous release, clicking on a cell in the risk matrix gadget fails to open a list of associated risks.
6.1.5-j7Jira Data Center 7.2.0 - 7.13.182021-03-31(Jira 7.x) Bug fix - FIXED: As of the previous release, clicking on a cell in the risk matrix gadget fails to open a list of associated risks.
6.1.5-j7Jira Server 7.2.0 - 7.13.182021-03-31(Jira 7.x) Bug fix - FIXED: As of the previous release, clicking on a cell in the risk matrix gadget fails to open a list of associated risks.
6.1.4Jira Data Center 8.0.0 - 8.16.12021-03-20(Jira 8.x) Bug fixes - [FIXED] Risk models page not loading unless Jira's base URL includes a context path.
- [FIXED] Deleting an impact or probability from the risk model does not delete the corresponding custom field option.
- [FIXED] Spurious warnings about a missing Backbone library in the log file.
6.1.4Jira Server 8.0.0 - 8.16.12021-03-20(Jira 8.x) Bug fixes - [FIXED] Risk models page not loading unless Jira's base URL includes a context path.
- [FIXED] Deleting an impact or probability from the risk model does not delete the corresponding custom field option.
- [FIXED] Spurious warnings about a missing Backbone library in the log file.
6.1.4-j7Jira Data Center 7.2.0 - 7.13.182021-03-20(Jira 7.x) Bug fixes - [FIXED] Risk models page not loading unless Jira's base URL includes a context path.
- [FIXED] Deleting an impact or probability from the risk model does not delete the corresponding custom field option.
6.1.4-j7Jira Server 7.2.0 - 7.13.182021-03-20(Jira 7.x) Bug fixes - [FIXED] Risk models page not loading unless Jira's base URL includes a context path.
- [FIXED] Deleting an impact or probability from the risk model does not delete the corresponding custom field option.
6.1.3Jira Data Center 8.0.0 - 8.15.12021-03-12(Jira 8.x) Bug fixes - FIXED: When Jira is configured to serve resources from a CDN, the settings page doesn't show icons correctly.
- FIXED: A 404 error raised on risk model screen when you delete a project that is associated with a risk register.
- FIXED: Searches not defaulting to jira.search.views.max.limit when jira.search.views.default.max is '0'.
6.1.3Jira Server 8.0.0 - 8.15.12021-03-12(Jira 8.x) Bug fixes - FIXED: When Jira is configured to serve resources from a CDN, the settings page doesn't show icons correctly.
- FIXED: A 404 error raised on risk model screen when you delete a project that is associated with a risk register.
- FIXED: Searches not defaulting to jira.search.views.max.limit when jira.search.views.default.max is '0'.
6.1.3-j7Jira Data Center 7.2.0 - 7.13.182021-03-12(Jira 7.x) Bug fixes - FIXED: When Jira is configured to serve resources from a CDN, the settings page doesn't show icons correctly.
- FIXED: A 404 error raised on risk model screen when you delete a project that is associated with a risk register.
- FIXED: Searches not defaulting to jira.search.views.max.limit when jira.search.views.default.max is '0'.
6.1.3-j7Jira Server 7.2.0 - 7.13.182021-03-12(Jira 7.x) Bug fixes - FIXED: When Jira is configured to serve resources from a CDN, the settings page doesn't show icons correctly.
- FIXED: A 404 error raised on risk model screen when you delete a project that is associated with a risk register.
- FIXED: Searches not defaulting to jira.search.views.max.limit when jira.search.views.default.max is '0'.
6.1.2Jira Data Center 8.0.0 - 8.15.12020-09-29(Jira 8.x) Avoid cluster lock contention This release fixes a bug that causes incoming connections to be blocked when used in conjunction with Automation for Jira, leading to eventual exhaustion of the server's resources.
6.1.2Jira Server 8.0.0 - 8.15.12020-09-29(Jira 8.x) Avoid server lock contention This release fixes a bug that causes incoming connections to be blocked when used in conjunction with Automation for Jira, leading to eventual exhaustion of the server's resources.
6.1.2-j7Jira Data Center 7.2.0 - 7.13.182021-01-09(Jira 7.x) Avoid server lock contention This release fixes a bug that causes incoming connections to be blocked when used in conjunction with Automation for Jira, leading to eventual exhaustion of the server's resources.
6.1.2-j7Jira Server 7.2.0 - 7.13.182021-01-09(Jira 7.x) Avoid server lock contention This release fixes a bug that causes incoming connections to be blocked when used in conjunction with Automation for Jira, leading to eventual exhaustion of the server's resources.
6.1.1Jira Data Center 8.0.0 - 8.12.32020-09-19(Jira 8.x) Stability at enablement This release fixes a bug that could cause instability during re-enablement of the app.
6.1.1Jira Server 8.0.0 - 8.12.32020-09-19(Jira 8.x) Stability at enablement This release fixes a bug that could cause instability during re-enablement of the app.
6.1.1-j7Jira Data Center 7.2.0 - 7.13.182020-09-19(Jira 7.x) Stability at enablement This release speeds up Jira re-indexing by improving the performance of custom field calculations.
It also fixes a bug that could cause instability during re-enablement of the app.
6.1.1-j7Jira Server 7.2.0 - 7.13.182020-09-19(Jira 7.x) Stability at enablement This release speeds up Jira re-indexing by improving the performance of custom field calculations.
It also fixes a bug that could cause instability during re-enablement of the app.
6.0.6Jira Data Center 8.0.0 - 8.12.32020-05-12(Jira 8.x) Bug fix - [FIXED] Error occurs on project settings page when the project uses the default workflow scheme.
6.0.6Jira Server 8.0.0 - 8.12.32020-05-12(Jira 8.x) Bug fix - [FIXED] Error occurs on project settings page when the project uses the default workflow scheme.
6.0.6-j7Jira Data Center 7.2.0 - 7.13.182020-05-12(Jira 7.x) Bug fix - [FIXED] Error occurs on project settings page when the project uses the default workflow scheme.
6.0.6-j7Jira Server 7.2.0 - 7.13.182020-05-12(Jira 7.x) Bug fix - [FIXED] Error occurs on project settings page when the project uses the default workflow scheme.
6.0.5Jira Data Center 8.0.0 - 8.8.12020-03-28(Jira 8.x) Bug fix - [FIXED] Risks sometimes appear in duplicate on the risk register and risk matrix.
6.0.5Jira Server 8.0.0 - 8.8.12020-03-28(Jira 8.x) Bug fix - [FIXED] Risks sometimes appear in duplicate on the risk register and risk matrix.
6.0.5-j7Jira Data Center 7.2.0 - 7.13.182020-03-28(Jira 7.x) Bux fix - [FIXED] Risks sometimes appear in duplicate on the risk register and risk matrix.
6.0.5-j7Jira Server 7.2.0 - 7.13.182020-03-28(Jira 7.x) Bug fix - [FIXED] Risks sometimes appear in duplicate on the risk register and risk matrix.
6.0.4Jira Data Center 8.0.0 - 8.8.12020-03-17(Jira 8.x) Bug fix - [FIXED] Risk Register panel not appearing in some circumstances.
6.0.4Jira Server 8.0.0 - 8.8.12020-03-17(Jira 8.x) Bug fix - [FIXED] Risk Register panel not appearing in some circumstances.
6.0.4-j7Jira Data Center 7.2.0 - 7.13.182020-03-17(Jira 7.x) Bug fix - [FIXED] Risk Register panel not appearing in some circumstances.
6.0.4-j7Jira Server 7.2.0 - 7.13.182020-03-17(Jira 7.x) Bug fix - [FIXED] Risk Register panel not appearing in some circumstances.
6.0.3Jira Data Center 8.0.0 - 8.7.12020-02-26(Jira 7.x) Fixes to risk register column sorting This release fixes two bugs that affected column-wise sorting of the risk register:
- [FIXED] Sorting the risk register by issue key doesn't treat the end of the key as numbers, so ABC-10 is higher in order than ABC-2.
- [FIXED] Sorting the risk register by inherent risk or residual risk arranges the list by issue key, not risk severity.
6.0.3Jira Server 8.0.0 - 8.7.12020-02-26(Jira 7.x) Fixes to risk register column sorting This release fixes two bugs that affected column-wise sorting of the risk register:
- [FIXED] Sorting the risk register by issue key doesn't treat the end of the key as numbers, so ABC-10 is higher in order than ABC-2.
- [FIXED] Sorting the risk register by inherent risk or residual risk arranges the list by issue key, not risk severity.
6.0.3-j7Jira Data Center 7.2.0 - 7.13.182020-02-26(Jira 7.x) Fixes to risk register column sorting This release fixes two bugs that affected column-wise sorting of the risk register:
- [FIXED] Sorting the risk register by issue key doesn't treat the end of the key as numbers, so ABC-10 is higher in order than ABC-2.
- [FIXED] Sorting the risk register by inherent risk or residual risk arranges the list by issue key, not risk severity.
6.0.3-j7Jira Server 7.2.0 - 7.13.182020-02-26(Jira 7.x) Fixes to risk register column sorting This release fixes two bugs that affected column-wise sorting of the risk register:
- [FIXED] Sorting the risk register by issue key doesn't treat the end of the key as numbers, so ABC-10 is higher in order than ABC-2.
- [FIXED] Sorting the risk register by inherent risk or residual risk arranges the list by issue key, not risk severity.
6.0.2Jira Data Center 8.0.0 - 8.7.12020-02-11(Jira 8.x) Bug fix - [FIXED] Blank exposure values were not being properly migrated to the new table structure used by version 6.0 of the add-on.
- [IMPROVED] Removed HTML formatting of Treatment field description consistent with disabling of HTML field descriptions by default in Jira 8.7.
6.0.2Jira Server 8.0.0 - 8.7.12020-02-11(Jira 8.x) Bug fix - [FIXED] Blank exposure values were not being properly migrated to the new table structure used by version 6.0 of the add-on.
- [IMPROVED] Removed HTML formatting of Treatment field description consistent with disabling of HTML field descriptions by default in Jira 8.7.
6.0.2-j7Jira Data Center 7.2.0 - 7.13.182020-02-10(Jira 7.x) Bug fix - [FIXED] Blank exposure values were not being properly migrated to the new table structure used by version 6.0 of the add-on.
6.0.2-j7Jira Server 7.2.0 - 7.13.182020-02-10(Jira 7.x) Bug fix - [FIXED] Blank exposure values were not being properly migrated to the new table structure used by version 6.0 of the add-on.
6.0.1Jira Data Center 8.0.0 - 8.6.12020-01-14(Jira 8.x) Bug fix for risk matrix dashboard gadget This release fixes a bug that caused risk matrix gadgets on the Jira dashboard to be displayed incorrectly in some circumstances.
6.0.1Jira Server 8.0.0 - 8.6.12020-01-14(Jira 8.x) Bug fix for risk matrix dashboard gadget This release fixes a bug that caused risk matrix gadgets on the Jira dashboard to be displayed incorrectly in some circumstances.
6.0.1-j7Jira Data Center 7.2.0 - 7.13.182020-01-14(Jira 7.x) Bug fix for risk matrix dashboard gadget This release fixes a bug that caused risk matrix gadgets on the Jira dashboard to be displayed incorrectly in some circumstances.
6.0.1-j7Jira Server 7.2.0 - 7.13.182020-01-14(Jira 7.x) Bug fix for risk matrix dashboard gadget This release fixes a bug that caused risk matrix gadgets on the Jira dashboard to be displayed incorrectly in some circumstances.
6.0.0Jira Data Center 8.0.0 - 8.6.12020-01-07(Jira 8.x) Multiple risk models - [NEW] The ability to define multiple risk models within a single Jira instance, and apply them selectively to Jira projects. Each model can have different dimensions, different values for each axis, and different levels of risk.
- [IMPROVED] The risk assessment panel has been overhauled to make it easier to work with. Click 'Modify' to begin making changes; click 'Cancel' to restore the assessment to its earlier state. No more spamming the issue history panel every time you move a slider.
6.0.0Jira Server 8.0.0 - 8.6.12020-01-07(Jira 8.x) Multiple risk models - [NEW] The ability to define multiple risk models within a single Jira instance, and apply them selectively to Jira projects. Each model can have different dimensions, different values for each axis, and different levels of risk.
- [IMPROVED] The risk assessment panel has been overhauled to make it easier to work with. Click 'Modify' to begin making changes; click 'Cancel' to restore the assessment to its earlier state. No more spamming the issue history panel every time you move a slider.
6.0.0-j7Jira Data Center 7.2.0 - 7.13.182020-01-11(Jira 7.x) Multiple risk models - [NEW] The ability to define multiple risk models within a single Jira instance, and apply them selectively to Jira projects. Each model can have different dimensions, different values for each axis, and different levels of risk.
- [IMPROVED] The risk assessment panel has been overhauled to make it easier to work with. Click 'Modify' to begin making changes; click 'Cancel' to restore the assessment to its earlier state. No more spamming the issue history panel every time you move a slider.
6.0.0-j7Jira Server 7.2.0 - 7.13.182020-01-11(Jira 7.x) Multiple risk models - [NEW] The ability to define multiple risk models within a single Jira instance, and apply them selectively to Jira projects. Each model can have different dimensions, different values for each axis, and different levels of risk.
- [IMPROVED] The risk assessment panel has been overhauled to make it easier to work with. Click 'Modify' to begin making changes; click 'Cancel' to restore the assessment to its earlier state. No more spamming the issue history panel every time you move a slider.
5.0.3Jira Data Center 8.0.0 - 8.6.12019-04-15(Jira 8.x) Compatibility update - [NEW] Add compatibility with Jira 8.1.0
5.0.3Jira Server 8.0.0 - 8.6.12019-04-15(Jira 8.x) Compatibility update - [NEW] Add compatibility with Jira 8.1.0
5.0.2Jira Data Center 8.0.0 - 8.0.32019-03-14(Jira 8.x) Risk register usability improvements - [NEW] Clicking on a risk in the risk register now opens that risk in a new tab by default. Users can elect to open risks in the current tab if they want.
- [NEW] Risk register view remembers view settings on a per-user basis.
- [FIXED] Cancel button not disabled while creating risk register.
5.0.2Jira Server 8.0.0 - 8.0.32019-03-14(Jira 8.x) Risk register usability improvements - [NEW] Clicking on a risk in the risk register now opens that risk in a new tab by default. Users can elect to open risks in the current tab if they want.
- [NEW] Risk register view remembers view settings on a per-user basis.
- [FIXED] Cancel button not disabled while creating risk register.
5.0.1Jira Data Center 8.0.0 - 8.0.32019-03-05(Jira 8.x) Data Center compatibility approval - [IMPROVED] Atlassian-approved compatibility with Jira Data Center.
- [FIXED] Various small bug fixes.
5.0.1Jira Server 8.0.0 - 8.0.32019-03-05(Jira 8.x) Various small bug fixes - [FIXED] Various small bug fixes.
- [IMPROVED] Atlassian-approved compatibility with Jira Data Center.
5.0.0Jira Server 8.0.0 - 8.0.32019-02-12(Jira 8.x) Compatibility with Jira 8 This release includes changes that make the app compatible with Jira 8.0.
4.5.3Jira Data Center 7.2.0 - 7.13.182019-10-08(Jira 7.x) Bug fix release - [FIXED] Risk assessment panel not properly sized when viewed in a Jira instance accessed via a reverse proxy.
- [FIXED] Risks not accessible in Jira 7.x using Microsoft IE 11.
- [IMPROVED] Various minor fixes and user interface adjustments.
4.5.3Jira Server 7.2.0 - 7.13.182019-10-08(Jira 7.x) Bug fix release - [FIXED] Risk assessment panel not properly sized when viewed in a Jira instance accessed via a reverse proxy.
- [FIXED] Risks not accessible in Jira 7.x using Microsoft IE 11.
- [IMPROVED] Various minor fixes and user interface adjustments.
4.5.2Jira Data Center 7.7.2 - 7.13.182019-03-14(Jira 7.x) Risk register usability improvements - [NEW] Clicking on a risk in the risk register now opens that risk in a new tab by default. Users can elect to open risks in the current tab if they want.
- [NEW] Risk register view remembers view settings on a per-user basis.
- [FIXED] Cancel button not disabled while creating risk register.
4.5.2Jira Server 7.7.2 - 7.13.182019-03-14(Jira 7.x) Risk register usability improvements - [NEW] Clicking on a risk in the risk register now opens that risk in a new tab by default. Users can elect to open risks in the current tab if they want.
- [NEW] Risk register view remembers view settings on a per-user basis.
- [FIXED] Cancel button not disabled while creating risk register.
4.5.0Jira Data Center 7.2.0 - 7.13.182019-03-04Data Center compatibility approval - [IMPROVED] Atlassian-approved compatibility with Jira Data Center.
- [FIXED] Various small bug fixes.
4.5.0Jira Server 7.2.0 - 7.13.182019-03-05Various small bug fixes - [FIXED] Various small bug fixes.
- [IMPROVED] Atlassian-approved compatibility with Jira Data Center.
4.4.3Jira Server 7.2.0 - 7.13.182018-11-26Minor bug fixes - [FIXED] Error messages shown during workflow transitions referred to custom fields by their default names, not their current (edited) names.
- [FIXED] Information message attached to "on the dashboard" link flashing on small screen sizes.
4.4.2Jira Server 7.2.0 - 7.12.32018-11-16Bug fix for project administrators - [FIXED] A bug made it impossible for a Project Administrator who is not also a global Jira Administrator to enable risk register for their project.
4.4.1Jira Server 7.2.0 - 7.12.32018-10-30Improved support for Jira Data Center - [FIXED] In clustered configurations of Jira Data Center, it was possible for database connections to be endlessly consumed during start-up.
4.4.0Jira Server 7.2.0 - 7.12.32018-10-10Bug fixes and performance improvements - [FIXED] Error 400 would appear after removing a risk assessment in some circumstances.
- [FIXED] Spurious warnings about parsing of exposure values were appearing in the log file.
- [FIXED] Renamed Treatment plan fields were appearing under their old names in the risk information panel.
- [IMPROVED] The list of risk registers (admin feature) has been dramatically simplified, and its rendering speed dramatically reduced. Risk register statuses can be checked by clicking through to individual risk register settings.
- [IMPROVED] Slider controls now show tick marks, representing underlying numeric values.
- [IMPROVED] Start-up times were reduced slightly for new users due to smaller JavaScript downloads.
4.3.10Jira Server 7.2.0 - 7.12.32018-08-12Adjust permission checks [FIXED] An error was reported when viewing the Risk registers page if the administrator did not have BROWSE permission on one of the projects.
4.3.9Jira Server 7.2.0 - 7.11.22018-08-10Fixes for two UI bugs - [FIXED] In the Firefox browser, the risk matrix would sometimes overlap the sidebar on smaller-sized windows.
- [FIXED] Some icons did not display because Jira was accessed from browsers that don't have Internet access.
4.3.8Jira Server 7.2.0 - 7.11.22018-08-08Bug fixes and performance improvement - [FIXED] The assessment panel doesn't appear in the following case: the residual assessment has been supplied, but no inherent assessment has been supplied.
- [FIXED] Strange characters prepended to 'Assess risk' button.
- [FIXED] Some special characters incorrectly escaped.
- [IMPROVED] Improved performance of assessment panel rendering.
4.3.7Jira Server 7.2.0 - 7.11.22018-07-20(Jira 7.2+) Bug fix [FIXED] Missing descriptions for field configurations could cause an error to occur when viewing add-on settings.
4.3.6Jira Server 7.2.0 - 7.11.22018-07-18(Jira 7.2+) Bug fix - [FIXED] An error occurred when creating a risk register for a project that has an issue type screen scheme with a NULL description.
4.3.5Jira Server 7.2.0 - 7.11.22018-07-13(Jira 7.2+) Bug fixes - [FIXED] Adjusted the alignment of icons on the Getting started page.
- [FIXED] The absence of a project lead caused an error to occur on the server.
- [IMPROVED] Better logging instrumentation for workflow transitions.
4.3.3Jira Server 7.2.0 - 7.11.22018-07-04(Jira 7.2+) Bug fix [FIXED] If the risk workflow specified in the add-on settings is deleted, a server-side error occurs when viewing the list of risk registers.
4.3.2Jira Server 7.2.0 - 7.10.22018-06-28(Jira 7.2+) Minor usability improvements - [IMPROVED] Minor usability improvements were made to the add-on settings page.
- [IMPROVED] Add-on start-up speed was increased.
4.3.1Jira Server 7.2.0 - 7.10.22018-06-24(Jira 7.2+) Bug fix [FIXED] A small number of users found that the add-on settings did not display properly after upgrading to version 4.3.0; this minor release fixes that problem.
4.3.0Jira Server 7.2.0 - 7.10.22018-06-23(Jira 7.2+) More flexible project configuration This release changes the way that risk registers are created and configured. Abandoning the previous one-size-fits-all approach, the add-on now permits greater latitude in regard to project settings for workflow usage, screen usage, and field configurations. Administrators can specify default project settings, and are warned if particular risk registers deviate from those defaults.
Minor adjustments have been made to the risk register views and risk assessment panels. Notably, slider controls (for editing impacts and probabilities) are now enabled by default; they can be turned off via the add-on settings.
4.2.5Jira Server 7.2.0 - 7.10.22018-04-25(Jira 7.2+) Bug fix [FIXED] Risk registers added to projects with keys matching JQL keywords (for example: 'IN' or 'IS') were not viewable; a status code 400 error appeared. This release fixes that problem.
4.2.4Jira Server 7.2.0 - 7.9.22018-03-12(Jira 7.2+) Bug fix [FIXED] A bug was fixed that prevented risk matrix gadgets from loading properly.
4.2.3Jira Server 7.2.0 - 7.8.42018-03-09(Jira 7.2+) Minor upgrade - [NEW] Added the 'Risk assessment' panel to the issue detail view so that you can use it directly from Boards.
- [NEW] Display a warning when slider controls are used on the same page as corresponding custom fields.
- [IMPROVED] Made the 'Risk assessment' panel easier to read on small devices.
- [FIXED] A bug was fixed that prevented the search index being updated in response to changes to risk assessments via slider controls.
4.2.2Jira Server 7.2.0 - 7.8.42018-02-08(Jira 7.2+) UI tweaks - [FIXED] The risk assessment panel now resizes itself more consistently when viewed in a project-centric tab.
- [IMPROVED] If the risk matrix is wider than the dashboard gadget in which it appears, a horizontal scrollbar is now provided.
- [IMPROVED] Blur support has been added to various custom fields. Changes to the field values are now registered when you tab or click away from them.
4.2.1Jira Server 7.2.0 - 7.7.42018-02-07(Jira 7.2+) Bug fix [FIXED] Fixed a bug that caused exposure colors to be set to gray when they were edited.
4.2.0Jira Server 7.2.0 - 7.7.42018-02-05(Jira 7.2+) Direct-to-navigator links - [NEW] Direct-to-navigator links: clicking a cell on the risk matrix gadget opens the Issue Navigator, and populates it with the risks that belong in that cell.
- [FIXED] Fixed a bug that caused Residual Exposure to sometimes appear out-of-sync with the Risk Register/Matrix view.
4.1.0Jira Server 7.2.0 - 7.7.42018-02-01(Jira 7.2+) Linked Treatments This release introduces the Linked Treatments feature.
- [NEW] Linked treatments: the risk register now displays other issues that will treat your risks.
- [FIXED] Risk matrix gadgets embedded in Confluence pages were failing to appear when Confluence and Jira were connected by OAuth or Trusted Applications connections.
- [FIXED] Residual Impact and Residual Probability fields were not being given sensible default values on the Treat transition screen.
- [IMPROVEMENT] Various minor bug fixes and user interface improvements.
4.0.4Jira Server 7.2.0 - 7.7.42018-01-25(Jira 7.2+) Fixes matrix gadget resizing [FIXED] A bug has been fixed that caused risk matrix gadgets to sometimes appear truncated. Those gadgets are now reliably re-sized immediately upon rendering.
4.0.3Jira Server 7.2.0 - 7.7.42018-01-24(Jira 7.2+) Minor update [IMPROVEMENT] Made the risk matrix gadget more resilient in the face of unexpected server errors.
4.0.2Jira Server 7.2.0 - 7.7.42018-01-24(Jira 7.2+) Bug fix [FIXED] We've fixed a bug introduced with version 4.0.0 that prevented risk matrix gadgets working when embedded in Confluence pages. We thought we'd fixed that bug in version 4.0.1, but that turned out not to be the case.
4.0.1Jira Server 7.2.0 - 7.7.42018-01-24(Jira 7.2+) Bug fix and performance improvement This is a bug-fix and performance release.
- [IMPROVED] Rendering of the risk register and risk matrix has been made sensitive to the system setting jira.search.views.default.max, which makes those functions faster.
- [FIXED] We've fixed a bug introduced with version 4.0.0 that prevented risk matrix gadgets working when embedded in Confluence pages.
4.0.0Jira Server 7.2.0 - 7.7.42018-01-19(Jira 7.2+) Major upgrade This is a major update to the product, incorporating changes to the appearance of the risk register and risk matrix; and providing a new way to edit risk factors: slider controls.
- [Improved] The risk matrix layout and appearance has been modernized and simplified.
- [New] The register view now has a sidebar that shows the risks in the currently-selected matrix cell.
- [Improved] The "Risks" project tab has been streamlined. Easier navigation between Original and Residual risk view.
- [Improved] Performance improvement: whereas earlier versions constructed risk matrices in server memory, causing slow rendering on very large Jira instances, and even server out-of-memory conditions in extreme cases, risk matrices are now constructed in browser memory.
- [New] The risk register (list) is now sortable by issue type, issue key, summary, status, treatment, exposure and residual exposure.
- [New] Slider controls are available as an optional alternative way to edit risk factors.
3.10.2Jira Server 7.0.0 - 7.7.42017-12-12(Jira 7.x) Bug fix This release fixes a bug that caused the column labels on certain dashboard gadgets to display incorrectly.
3.10.1Jira Server 7.0.0 - 7.6.172017-11-20(Jira 7.x) Bug fixes and minor improvements - NEW: If a searcher has not been configured for one of the custom fields managed by the add-on, a warning message is now displayed.
- FIXED: If a pie chart gadget was added to a Dashboard and configured to display Exposure statistics, the legend of that chart presented the Exposure values as HTML code. That bug has now been fixed, and pie charts now show Exposure names.
- FIXED: The information panel that appears on the right-hand side of the Issue View page used to be hard-coded with "impact" and "probability"; now they show the actual names of those custom fields, even if they've been renamed since installation.
- IMPROVED: Risks are now listed on risk registers even if they have not yet been assigned an impact or probability value.
3.10.0Jira Server 7.0.0 - 7.6.172017-11-18(Jira 7.x) Compatibility with Jira 7.6.0 This release makes adjustments to ensure compatibility with Jira 7.6.0; specifically: it allows the priority field to be available on the Risk Edit screen, or to be removed from that screen by an administrator.
3.9.0Jira Server 7.0.0 - 7.5.42017-06-16(Jira 7.x) Flip axes of risk matrix - [NEW] The axes of the risk matrix can now be flipped: you can view Probability on the X axis and Impact on the Y axis, or vice versa. Make your choice on the Settings page in the add-on's administration section.
- [FIXED] The little question mark next to the Treatment field on the Create Issue dialog was not displaying the relevant help text when that dialog was opened in a pop-up.
- [FIXED] If an attempt to reset the workflow was made before any risk registers were created, an error message appeared.
- [IMPROVED] The "Original risk" and "Residual risk" headings on the risk register were hard-coded; we've now made them dynamic so that the headings correspond to the names of the relevant custom fields.
3.8.1Jira Server 7.0.0 - 7.3.92017-05-22(Jira 7.x) Ensure all risk register issues appear in navigator FIXED: This fix ensures that the result of clicking on "view these risks in the issue navigator" shows you the same risks as the risk register.
3.8.0Jira Server 7.0.0 - 7.3.92017-05-22(Jira 7.x) Associate risk with any issue type - NEW: The risk register and risk matrix now show any issues that have values for the Impact and/or Probability fields, not just issues that have the 'Risk' type. That means you can manually associate Impact and Probability custom fields with other issue types, and have those issues presented as risks.
- FIXED: We now ensure that the default issue type scheme includes the 'Risk' issue type. Previously, the absense of the that issue type in the default issue type scheme could prevent risks being moved between projects.
3.7.0Jira Server 7.0.0 - 7.3.92017-05-09(Jira 7.x) Cosmetic enhancements This release includes three minor enhancements:
- NEW: Matrix axes are now labelled with the names of the Impact and Probability custom fields, taking into account their translations if any.
- NEW: The 'Contact ProjectBalm' link has been replaced with a 'Get support' link, which takes the user to the Risk Register support portal.
- NEW: The new Risk Register logo now appears in several locations.
3.6.2Jira Server 7.0.0 - 7.3.92017-04-04(Jira 7.x) Make searches cope with Exposure field name changes FIXED: Renaming the Exposure field caused searches initiated from the Statistics gadget to be incorrectly formed. This fix causes searches based on the Exposure field to use the field's id rather than its name, which may have been changed.
3.6.1Jira Server 7.0.0 - 7.3.92017-03-24(Jira 7.x) Minor bugs fixed This release fixes a couple of minor bugs:
- FIXED: Now the Exposure delete button appears unless there is only one remaining exposure.
- FIXED: The add-on was adopting for its own use certain pre-existing custom fields: Impact, Probability, Treatment, etc; causing problems for customers who had previously installed other risk management products. Now the add-on always creates its owncustom fields.
- NEW: A licensing attribution page has been added in compliance with Open Software licensing conditions.
- IMPROVED: The section heading on the administration page has been changed.
3.6.0Jira Server 7.0.0 - 7.3.92017-01-21(Jira 7.x) Configurable appearance of empty matrix cells This release introduces the ability for administrators to choose the appearance of empty cells on the risk matrix: either blank (filled with white), or filled with the color assigned to the exposure level at that position.
3.5.6Jira Server 7.0.0 - 7.3.92016-12-25(Jira 7.x) Validate screens with multiple tabs FIXED: If an administrator moved one of the custom fields created by the add-on to a different tab, the risk registers were marked as 'Broken'. Now that this bug has been fixed, administrators are free to arrange their screen tabs to include risk-related custom fields, and their risk registers will remain 'Intact'.
3.5.5Jira Server 7.0.0 - 7.3.92016-12-16(Jira 7.x) Improve search robustness This release fixes a bug that caused some risk searches to fail if particular custom fields were manually renamed by an administrator.
3.5.4Jira Server 7.0.0 - 7.3.92016-10-01(Jira 7.x) Eliminate spurious error messages in log - [FIXED] Spurious error messages were occasionally appearing in the Jira log file, complaining that a project id could not be parsed. This didn't affect functionality of the add-on.
- [FIXED] The risk matrix occasionally failed to appear on the project tab until a manual page refresh was performed.
3.5.3Jira Server 7.0.0 - 7.3.92016-09-22(Jira 7.x) Amend administration permission checks [FIXED] Neither project administrators nor global administrators were able to administer risk registers on the Risk Registers page unless they also had permission to browse issues in those projects.
3.5.2Jira Server 7.0.0 - 7.3.92016-09-18(Jira 7.x) Dashboard gadget discoverability [IMPROVED] This release improves discoverability of the risk matrix dashboard gadget.
[FIXED] In Jira 7.2+, the Residual Impact and Residual Probability custom fields were not defaulting to their Original risk counterparts.
3.5.1Jira Server 7.0.0 - 7.3.92016-09-14(Jira 7.x) Isolation of issue type screen schemes This is primarily a bug-fix release:
- [FIXED] Issue type screen schemes that were shared by multiple projects were not being properly isolated (split to ensure other projects are unaffected) during risk register creation.
- [FIXED] Risk registers were not being automatically deleted upon deletion of their corresponding projects.
- [IMPROVED] Logging levels have been adjusted so that more information is logged during risk register creation.
3.5.0Jira Server 7.0.0 - 7.3.92016-08-27(Jira 7.x) Residual Risk - [NEW] Residual risk: you can now record the risk remaining after treatment will have been applied. The risk matrix (gadget, project tab, or report) can be configured to show residual risk or original risk.
- [NEW] Each risk matrix can be individually configured to show risk counts or risk keys.
- [IMPROVED] When a matrix cell contains a link to '1 risk', that link now takes the user to the Issue View page directly.
- [IMPROVED] Matrices are now better positioned within dashboard gadget containers.
- [IMPROVED] To reduce clutter in the Issue Navigator, filters are no longer automatically created when risk registers are added to projects.
- [IMPROVED] Performance has been improved by minimizing the application of cross-cluster locking (for Data Center installations of Jira).
- [IMPROVED] The risk matrix report has been moved into the 'Issue Analysis' section.
- [FIXED] The Risk Matrix Report heading used to refer to the wrong project under some circumstances.
3.4.2Jira Server 7.0.0 - 7.1.102016-08-05(Jira 7.x) Bug fixes - [FIXED] Clicking the link inside a matrix cell would display risks in the Issue Navigator using an incorrect filter: risks from other projects would be displayed in some circumstances.
- [FIXED] When viewing one of the transitions of the Risk Workflow, one of the validators was incorrectly named.
- [FIXED] The "Get Started" link for new installations was taking the user to the Help page rather than the Risk Registers page.
- [NEW] A link to the Risk Register FAQ has been added to the administration page.
3.4.0Jira Server 7.0.0 - 7.1.102016-07-12(Jira 7.x) Support manual changes to the risk workflow [NEW] This release allows any manual changes to the risk workflow to persist, whereas previously any changes to the workflow were automatically undone whenever a user created a new risk register. A 'Reset risk workflow' button has been added to the 'Risk Register settings' page. Clicking that button returns the risk workflow to its original configuration.
[FIXED] A bug that caused workflows to sometimes appear as 'inactive' even though they are linked to Jira projects has been fixed.
3.3.2Jira Server 7.0.0 - 7.1.102016-07-06(Jira 7.x) Adjust matrix cell rendering This release fixes a bug that caused the contents of risk matrix cells to appear off-center when viewed in some browsers, including Firefox.
3.3.1Jira Server 7.0.0 - 7.1.102016-06-22(Jira 7.x) Show risk counts in matrix This release simplifies the risk matrix view, which can become cluttered and distended if many risks are represented there. The improvements include:
- Risk counts are now shown in the matrix by default. Click on a risk count to view the individual risk issues for that cell. Return to the earlier style via the Settings page in the admin area.
- Matrix row and column headings can optionally be hidden on the dashboard matrix gadget.
- Release notes and help information can now be found in the admin area.
3.2.0Jira Server 7.0.0 - 7.1.102016-06-01 (Jira 7.x) Consolidation This release consolidates the administration screens, improving their layout, their menus, and so on. It also introduces risk adoption: pre-existing Risk issues are adopted upon creation of the first risk register.
These bug were fixed:
- [FIXED] a pre-existing Impact custom field is adopted without checking its type
- [FIXED] the risk matrix gadget title and description don't appear properly in the macro browser when Jira is running behind an proxy server, and when embedding the gadget in a Confluence page.
These improvements come on the back of other recent enhancements: Risk model, Exposure customization, Searchable exposures, and Manifest.
3.1.0Jira Server 7.0.0 - 7.1.102016-05-20(Jira 7.x) Custom exposures You can now customize the set of exposures that are mapped in the risk model. Add new ones, rename existing ones, change their colors, and change their severity ordering. Your changes will be reflected in the risk register view and in the matrix views.
3.0.1Jira Server 7.0.0 - 7.1.102016-04-13(Jira 7.x) Bug fixes Bug fixes in version 3.0.1:
- Fixed: exposure not appearing in Jira Issues gadget in Confluence
- Fixed: risk issue type mistakenly added to default issue type scheme
- Fixed: project picker includes projects that already have a risk register
- Fixed: project picker spins endlessly if there are no projects
(Version 3.0.0) Makes risk management easier for organizations that have finer-grained risk models. It also integrates risks more seamlessly into the Issue Navigator.
New features:
- Changing the risk model: make your matrix 4x4, 5x5, 3x6, or any dimensions you like.
- Use Exposure as a term in your issue search filters, and get risk statistics by Exposure.
- Manifest: a diagnostic tool that shows behind-the-scenes configuration data
3.0.0Jira Server 7.0.0 - 7.1.102016-04-02(Jira 7.x) Risk model customization This is a major release of the add-on to make risk management easier for organizations that have finer-grained risk models. It also integrates risks more seamlessly into the Issue Navigator.
New features:
- Changing the risk model: make your matrix 4x4, 5x5, 3x6, or any dimensions you like.
- Use Exposure as a term in your issue search filters, and get risk statistics by Exposure.
- Manifest: a diagnostic tool that shows behind-the-scenes configuration data
1.10.0Jira Server 6.3 - 6.4.142017-06-16(Jira 6.x) Flip axes of risk matrix - [NEW] The axes of the risk matrix can now be flipped: you can view Probability on the X axis and Impact on the Y axis, or vice versa. Make your choice on the Settings page in the add-on's administration section.
- [FIXED] The little question mark next to the Treatment field on the Create Issue dialog was not displaying the relevant help text when that dialog was opened in a pop-up.
- [FIXED] If an attempt to reset the workflow was made before any risk registers were created, an error message appeared.
- [IMPROVED] The "Original risk" and "Residual risk" headings on the risk register were hard-coded; we've now made them dynamic so that the headings correspond to the names of the relevant custom fields.
1.9.0Jira Server 6.3 - 6.4.142017-05-22(Jira 6.x) Associate risk with any issue type - NEW: The risk register and risk matrix now show any issues that have values for the Impact and/or Probability fields, not just issues that have the 'Risk' type. That means you can manually associate Impact and Probability custom fields with other issue types, and have those issues presented as risks.
- FIXED: We now ensure that the default issue type scheme includes the 'Risk' issue type. Previously, the absense of the that issue type in the default issue type scheme could prevent risks being moved between projects.
1.8.0Jira Server 6.3 - 6.4.142017-05-09(Jira 6.x) Cosmetic enhancements This release includes three minor enhancements:
- NEW: Matrix axes are now labelled with the names of the Impact and Probability custom fields, taking into account their translations if any.
- NEW: The 'Contact ProjectBalm' link has been replaced with a 'Get support' link, which takes the user to the Risk Register support portal.
- NEW: The new Risk Register logo now appears in several locations.
1.7.2Jira Server 6.3 - 6.4.142017-04-04(Jira 6.x) Make searches cope with Exposure field name changes FIXED: Renaming the Exposure field caused searches initiated from the Statistics gadget to be incorrectly formed. This fix causes searches based on the Exposure field to use the field's id rather than its name, which may have been changed.
1.7.1Jira Server 6.3 - 6.4.142017-03-24(Jira 6.x) Minor bugs fixed This release fixes a couple of minor bugs:
- FIXED: Now the Exposure delete button appears unless there is only one remaining exposure.
- FIXED: The add-on was adopting for its own use certain pre-existing custom fields: Impact, Probability, Treatment, etc; causing problems for customers who had previously installed other risk management products. Now the add-on always creates its own custom fields.
- NEW: A licensing attribution page has been added
- IMPROVED: The menu item labels on the administration page have been changed.
1.7.0Jira Server 6.3 - 6.4.142017-01-21(Jira 6.x) Configurable appearance of empty matrix cells This release introduces the ability for administrators to choose the appearance of empty cells on the risk matrix: either blank (filled with white), or filled with the color assigned to the exposure level at that position.
1.6.6Jira Server 6.3 - 6.4.142016-12-25(Jira 6.x) Validate screens with multiple tabs FIXED: If an administrator moved one of the custom fields created by the add-on to a different tab, the risk registers were marked as 'Broken'. Now that this bug has been fixed, administrators are free to arrange their screen tabs to include risk-related custom fields, and their risk registers will remain 'Intact'.
1.6.5Jira Server 6.3 - 6.4.142016-12-16(Jira 6.x) Improve search robustness This release fixes a bug that caused some risk searches to fail if particular custom fields were manually renamed by an administrator.
1.6.4Jira Server 6.3 - 6.4.142016-10-01(Jira 6.x) Eliminate spurious error messages in log - [FIXED] Spurious error messages were occasionally appearing in the Jira log file, complaining that a project id could not be parsed. This didn't affect functionality of the add-on.
1.6.3Jira Server 6.3 - 6.4.142016-09-22(Jira 6.x) Amend administration permission checks [FIXED] Neither project administrators nor global administrators were able to administer risk registers on the Risk Registers page unless they also had permission to browse issues in those projects.
1.6.2Jira Server 6.3 - 6.4.142016-09-18(Jira 6.x) Dashboard gadget discoverability [IMPROVED] This release improves discoverability of the risk matrix dashboard gadget.
1.6.1Jira Server 6.3 - 6.4.142016-09-14(Jira 6.x) Isolation of issue type screen schemes This is primarily a bug-fix release:
- [FIXED] Issue type screen schemes that were shared by multiple projects were not being properly isolated (split to ensure other projects are unaffected) during risk register creation.
- [FIXED] Risk registers were not being automatically deleted upon deletion of their corresponding projects.
- [IMPROVED] Logging levels have been adjusted so that more information is logged during risk register creation.
1.6.0Jira Server 6.3 - 6.4.142016-08-30(Jira 6.x) Residual Risk - [NEW] Residual risk: you can now record the risk remaining after treatment will have been applied. The risk matrix (gadget, project tab, or report) can be configured to show residual risk or original risk.
- [NEW] Each risk matrix can be individually configured to show risk counts or risk keys.
- [IMPROVED] When a matrix cell contains a link to '1 risk', that link now takes the user to the Issue View page directly.
- [IMPROVED] Matrices are now better positioned within dashboard gadget containers.
- [IMPROVED] To reduce clutter in the Issue Navigator, filters are no longer automatically created when risk registers are added to projects.
- [IMPROVED] Performance has been improved by minimizing the application of cross-cluster locking (for Data Center installations of Jira).
- [FIXED] The Risk Matrix Report heading used to refer to the wrong project under some circumstances.
1.5.2Jira Server 6.3 - 6.4.142016-08-05(Jira 6.x) Bug fixes - [FIXED] Clicking the link inside a matrix cell would display risks in the Issue Navigator using an incorrect filter: risks from other projects would be displayed in some circumstances.
- [FIXED] When viewing one of the transitions of the Risk Workflow, one of the validators was incorrectly named.
- [FIXED] The "Get Started" link for new installations was taking the user to the Help page rather than the Risk Registers page.
- [NEW] A link to the Risk Register FAQ has been added to the administration page.
1.5.0Jira Server 6.3 - 6.4.142016-07-12(Jira 6.x) Support manual changes to the risk workflow [NEW] This release allows any manual changes to the risk workflow to persist, whereas previously any changes to the workflow were automatically undone whenever a user created a new risk register. A 'Reset risk workflow' button has been added to the 'Risk Register settings' page. Clicking that button returns the risk workflow to its original configuration.
[FIXED] A bug that caused workflows to sometimes appear as 'inactive' even though they are linked to Jira projects has been fixed.
1.4.1Jira Server 6.3 - 6.4.142016-07-06(Jira 6.x) Adjust matrix cell rendering This release fixes a bug that caused the contents of risk matrix cells to appear off-center when viewed in some browsers, including Firefox.
1.4.0Jira Server 6.3 - 6.4.142016-06-22(Jira 6.x) Show risk counts in matrix This release simplifies the risk matrix view, which can become cluttered and distended if many risks are represented there. The improvements include:
- Risk counts are now shown in the matrix by default. Click on a risk count to view the individual risk issues for that cell. Return to the earlier style via the Settings page in the admin area.
- Matrix row and column headings can optionally be hidden on the dashboard matrix gadget.
- Release notes and help information can now be found in the admin area.
1.3.0Jira Server 6.3 - 6.4.142016-06-01(Jira 6.x) Consolidation This release consolidates the administration screens, improving their layout, their menus, and so on. It also introduces risk adoption: pre-existing Risk issues are adopted upon creation of the first risk register.
These bug were fixed:
- [FIXED] a pre-existing Impact custom field is adopted without checking its type
- [FIXED] the risk matrix gadget title and description don't appear properly in the macro browser when Jira is running behind an proxy server, and when embedding the gadget in a Confluence page.
These improvements come on the back of other recent enhancements: Risk model, Exposure customization, Searchable exposures, and Manifest.
1.2.0Jira Server 6.3 - 6.4.142016-05-20(Jira 6.x) Custom exposures You can now customize the set of exposures that are mapped in the risk model. Add new ones, rename existing ones, change their colors, and change their severity ordering. Your changes will be reflected in the risk register view and in the matrix views.
1.1.1Jira Server 6.3 - 6.4.142016-04-27(Jira 6.x) Bug fix - administration permission [FIXED] a bug that limited Administrator access to plugin administration features, permitting only System Administrators to configure risk registers and change the risk model.
1.1.0Jira Server 6.3 - 6.4.142016-04-14(Jira 6.x) Risk model customization and bug fixes This release is compatible with Jira 6.3 - 6.4. It makes risk management easier for organizations that have finer-grained risk models. It also integrates risks more seamlessly into the Issue Navigator.
New features:
- Changing the risk model: make your matrix 4x4, 5x5, 3x6, or any dimensions you like.
- Use Exposure as a term in your issue search filters, and get risk statistics by Exposure.
- Manifest: a diagnostic tool that shows behind-the-scenes configuration data