Jira Automation trigger when value changes for Score?

[Todd Iorio]

I have a simple automation to set Priority when the value for Score is between certain thresholds. The trigger is set "When: Value Changes for Score" however the automation never gets triggered when I update the Score values via backlog prioritization.

If I set the trigger to 'manual' and then run the automation on an issue manually it performs perfectly, reading the Score value and then setting the priority on the ticket.

I'm unsure how to get the automation to trigger whenever the Score value is updated automatically however. Thanks for any suggestions.

[Bill Sheboy]

Hi @Todd Iorio 

Do you have one automation rule setting the Score and another setting the Priority...and the second one is not triggering?

If so, your two options to solve this are:

1. Look at the rule details section for the Priority setting rule, and enable the option "Allow Rule Trigger"
2. Combine the rules to perform the updates in one rule

Kind regards,
Bill

[Todd Iorio]

Thanks Bill, I do not have a rule that is modifying score, we are utilizing Backlog Prioritization to set the Score value, or setting it when a ticket is created in the ticket detail.

[Bill Sheboy]

Thanks for that information, Todd.

So you are manually setting the Score value and that change is not being detected, correct? Or do you mean there is also some addon named Backlog Prioritization which is helping to set the Score field?

[Todd Iorio]

well both actually...

we are utilizing the backlog prioritization in Jira here

BUT we also set score in the ticket detail here:

Neither triggers the automation...

[Bill Sheboy]

Thanks!  Some field changes do not trigger rules/cannot be seen by that Issue Field trigger.

Let's try this instead...please create a new test rule with these components:

• trigger: issue updated
• advanced compare condition: 
  • first value: {{#changelog.score}}{{fromString}}{{/}}
  • condition: does not equal
  • second value: empty
• action: write to something to the audit log, such as "Score Changed!"

Now make a Score change, check the audit log, and see if the rule worked as expected.  If it does you can use that trigger and condition to detect Score changes.

If that does not catch the change, please use this how-to article to confirm the smart value name for your Score field, including the capitalization: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/  And if necessary, use the custom field ID for the smart value instead.

If after those steps you cannot detect a change to Score, there is something special about the field, and I'd recommend working with your site admin to submit a support ticket to Atlassian and/or the vendor of that addon.

[Todd Iorio]

The automation is not triggering. If I set the trigger to manual, and run the automation on an issue manually it executes. However it will not trigger automatically. Here is the setup:

[Jack Brickey]

Is it not triggering or not passing a condition? If not triggering then check carefully the trigger.

[Fabian Lim]

Hi @Todd Iorio

Please share the details of your rule so that we can help. The condition with the thresholds will help the most.

Regards

[Todd Iorio]

sorry I meant to reply here but posted the reply as an answer above instead...

The automation is not triggering. If I set the trigger to manual, and run the automation on an issue manually it executes. However it will not trigger automatically. Here is the setup: