Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How do I use Backlog Prioritization score in Jira automation?



I'm using Backlog Prioritization plugin.

I would like to perform some action every time the "Score" field is updating via the plugin, using Jira automation.

I'm using "Field value changed" as a trigger, but it seems that Jira automation does catch the trigger when "Score" field is being change view the Backlog Prioritization plugin.


Any idea how to resolve this?

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 30, 2022

Hi @Sarit Ashtar -- Welcome to the Atlassian Community!

First thing: as you are using a marketplace addon and asking about automation rules, I suggest checking the vendor's documentation to learn what is supported.  Some addons have calculated fields which may not be accessible from rules.

Whilst waiting for an answer from the vendor, you can try this how-to article to learn if a field has a supported smart value for rules, and the exact name to use:

Next...for your trigger: some custom fields are not listed for the Issue Field Updated trigger.  In that case, please try the generic Issue Updated trigger and then use the {{changelog}} values for your field to determine if the {fromString}} and {{toString}} differ, as that would indicate the field was updated.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events