How do I use Backlog Prioritization score in Jira automation?

Sarit Ashtar November 29, 2022

Hi,

 

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?

2 answers

0 votes
Andy Tran August 20, 2024

@Sarit Ashtar were you ever able to figure this out?  I'm attempting to message the app creator support group but ran across your post.

Andy Tran August 20, 2024

Disregard

Sarit Ashtar August 21, 2024

@Andy Tran  hi Andy. unfortunately, no. seems like the "Score"  field does not trigger the "Field value changed" in Jira automation.

Instead, I have created a regular custom field called "Priority Score", and a daily automation which checks the value of both fields. 

In case they are different, it means someone changed the "Score", so I copy the new "Score" into "Priority Score"

image.png

Like Andy Tran likes this
Andy Tran August 21, 2024

Thank you for the feedback.

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.
November 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: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

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,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events