Updating Custom Field with Sum of other custom fields

[Wayne Moore]

I would like to calculate the ICE score for an issue in Jira. This value is obtained by adding the values of three separate fields (Impact, Confidence and Ease) and then dividing them by 3. This value I would like to have calculated and added to the custom field ICE score. Is this possible in Jira and if so, how do I go about it? Thanks in advance.

[Piyush A (STR)]

Hello @Wayne Moore 

Welcome to the community!!

out of box -no option to do it, but using additional plugins we can

anyhow, with jira cloud - we’ve option Automation (in jira cloud for project admin)

process as rule:

• Select project
• OR condition for issue field update for those 3 fields
• edit issue option and set the value of final field as
• ({{issue.customfield_16943}+{{issue.customfield_16719}}+{{issue.customefield_1234}})/3
• save and publish the rule

ref for automation in jira https://www.atlassian.com/software/jira/automation-template-library/rules

[Alex David]

Hey Wayne, Piyush's rule is the right shape, and using customfield IDs the way he did is the important detail. Name based smart values get flaky as soon as a field name has punctuation in it, or a team-managed project makes its own copy of the field.

Two things worth adding if you're going to live with that rule. Wrap the arithmetic in {{#=}} ... {{/}} so it actually evaluates, otherwise the expression comes back as text and the field either stays empty or fills with the formula. And put a default on each input, like {{issue.customfield_16943|0}}, because a half-scored issue otherwise resolves to ( + 4 + 2 ) / 3 and the rule errors rather than skipping.

The other thing to decide up front is what happens on a bulk edit or a CSV import that updates existing issues. Field value changed won't fire for those, so the score quietly goes stale on exactly the issues you touched in bulk. A second rule on a scheduled trigger over a JQL filter covers the backfill, and it also saves you re-running things by hand whenever you change the model.

Full disclosure, I work on Product Management Priority Scoring for Jira at ChefStackz. If you'd rather not own a formula rule at all, it does ICE on the issue itself, along with RICE and WSJF, and writes the result to a normal Jira number field so it stays sortable in JQL: https://marketplace.atlassian.com/apps/3064060819/product-management-priority-scoring-for-jira

Either way the number is only as good as the scale behind it. Worth agreeing what a 3 versus a 5 means for Ease before anyone starts scoring, otherwise you end up with a tidy field full of numbers nobody quite trusts.

Alex