Create Automation from Impact Score

[Corey Hampton]

Can anyone help with the Impact Score calculation and using it in automation rules? It's quite frustrating to have fields like Impact Score that I can't access the actual value for because it's a calculation and not stored in the database. 

Here's what I'm trying to do. 

• When the Impact Score is >= 25
  • Set the custom field of DACI Required to Yes
  • Add comment that DACI is required
• When the Impact Score is < 25
  • Set the custom field of DACI Required to No

Here's my problem. Impact Score value isn't actually stored. I tried to re-fetch data from the Idea and log the Impact Score value, which always comes back blank. 
Instead, I tried to calculate the Impact Score manually in the rule, but I don't have the proper calculation because it doesn't match the actual Impact Score. 

How can I solve for the Impact Score?

Any insight into Atlassian storing this value in the future? Or why fields like this are created that can't be used in automation? 

[Fabian Lim · Accepted solution]

Hi @Corey Hampton

I would consider creating a new custom field that determines the value of impact score.  For example for Change Enablement, we calculate the Risk Level Calculation where customers answer several questions on the form and then use automation to calculate its score.  We then use the value to determine which transition should be used for a CAB Review, Multiple approvals, or no approvals.

In your scenario, you can build your own impact score formula.  

Fabian

[Corey Hampton]

Thank you Fabian, I figured that's what I will have to do.  It's unfortunate, but guess I don't have a choice.

[Bill Sheboy]

Hi @Corey Hampton 

While I believe you can export the Impact Score (as described in this other question's answers), it cannot be accessed within a rule as it is one of those display-only, UX values.

Perhaps @Tanguy Crusson can comment if accessing such values is on the roadmap items as I did not see it there.

Kind regards,
Bill

[Corey Hampton]

Thank you Bill, but the link you provided doesn't help. It's to export data to a CSV file, which won't help with automation. 

I've seen it mention in multiple threads that fields like Impact Score will be updated in the future to function like 'normal' Jira fields but with no progress. Oldest comment I found was from almost 3 years ago (2023) so it doesn't appear that anything has changed. 

[Bill Sheboy]

Yes, and...until the JPD team members comment on making calculated fields available in rules, the workaround I have seen in other threads is guessing how Atlassian implements the field and experimenting to recreate that logic in an automation rule's logic.

[Kamila Czubaj]

Hey,

We are working on persisting the Formula fields, witch will unlock the JQL and Automation usage of them.  

[Corey Hampton]

@Kamila Czubaj Do you have a timeline? I've seen on other threads that Atlassian is working on it but no mention of a timeline.