Automation Maths using Original Estimate

Phil Skade March 27, 2024

So I'm trying to use Jira Automation to do a simple Value / Effort calculation. 

We use a field "Priority Score" to represent value and we use the Jira "Original Estimate" field to represent the effort. 

I want to divide one by the other. 

After some trial and error I've landed on the following which is intended to populate the numeric field "Net Priority Score" whenever an issue is updated. 

{{#=}}{{issue.fields.priority score.divide.issue.fields.originalestimate}}{{/}}

I look in the Automation audit log which proudly tells me "SUCCESS".

However when I then look at the issue I edited, the "Net Priority Score" is simply null. 

I can confirm the 2 fields in the calculation both have values defined

Send help.image.png

3 answers

1 accepted

0 votes
Answer accepted
Phil Skade March 28, 2024

Resolved it with the following expression and putting the expression in the top box not the bottom one.. woops 


{{#math}}{{issue.priority score}}/({{issue.original estimate}}/28800){{/math}}

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.
March 27, 2024

Hi @Phil Skade 

Please review the math expression documentation as your rule appears to have some errors:

And also...Your rule's edit action has both selected the field from the dropdown list and is trying to update it with advanced edit with JSON.  That is not possible: pick one method to update the field, such as using only the dropdown selection.

Kind regards,

Phil Skade March 28, 2024

Thanks for the latter tip, moved the edit action up a box. Hasn't entirely fixed it but getting there. 

Like Bill Sheboy likes this
0 votes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 27, 2024

Hi @Phil Skade 

please refer to this sample:

{{issue.timetracking.timeSpentSeconds.divide(3600).divide(issue.Request participants.size)}}

Maybe you can try:

{{issue.priority score.divide(issue.originalestimate)}}

You could test if score and estimate field vlaues can be got firstly if you have any issue.


Hope it helps.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events