Risk Register - Applying Automation to Risk Changes

[sleipper]

I'm looking to add some Jira automation to fields the custom fields of:

• Inherent risk
• Inherent probability
• Inherent impact

These gets changed using the slider as shown at http://docs.projectbalm.com/risk-register-user-guide-(cloud)/creating-and-assessing-risks/ however the changes to the field values don't trigger the "field value changed" within Jira Automation.

[Stefan Lopes]

Hi @Craig Schwarze _ProjectBalm_

do you have any updates on this?

[Craig Schwarze _ProjectBalm_]

We are currently migrating our product to Atlassian's new Forge platform. Once this is complete, it will enable us to resolve this issue. I cannot give you a timeframe, but we will notify all customers when it is done.

[Chris Gripton]

Hi @Craig Schwarze _ProjectBalm_ 

Any update on this one please?

[Craig Schwarze _ProjectBalm_]

Hi Chris,

The Forge migration is proceeding. We've already released some components of our system on Forge, though these do not yet enable you to trigger automation scripts.

I can't give you a timeline, but I can tell you it is our top priority. All customers will be informed once this capability is available.

kind regards,
Craig

[Chris Gripton]

Hi Craig,
Happy new year

Any joy on this one please?

I would really like to use Risk Register on our project, but I don't want to have Inherent priority separate from Jira Priority.

Best,
Chris

[Craig Schwarze _ProjectBalm_]

Hi Chris,

The Forge/ROA migration, which will enable this, is progressing well. It is our top priority and we are expending significant resource on it. At the same time, it is complex and time-consuming. I can't give you a date, but there are still a few months of work to go.

We will notify all of our clients once this is available.

kind regards,
Craig

[Chris Gripton]

Thanks for the update Craig,

Good luck with the migration. 

[Craig Schwarze _ProjectBalm_]

Hello!

Unfortunately, due to some platform limitations, those fields do not currently trigger Jira Automation upon changes. We are currently working on some enhancements that will resolve this issue. While I can't give you an exact date, we hope to have more news soon.

kind regards,
Craig Schwarze
[ProjectBalm]