nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Calculated field in the cloud

Chris_cb7wvp

I've got two custom fields:

1. Consequence

2. Probability

Both of which are a numerical value from 1-5.

I'll be making a third custom field that should show the result of fields 1 and 2 multiplied.

I've been reading about some workarounds for calculation in Cloud instances, but they're mostly about counting transitions through a workflow.

Has anyone here done such a setup before, or have any advice?

I've already been through the suggestions here but haven't been able to sort this out yet.

Accepted answers

Gaurav_0av1h6

Hello @Chris

As suggested in the Atlassian article, this can be achieved using Automation.

The steps to set up the Automation are as:

Go to Project Settings
From the left-hand menu, select Automation
Click on 'Create Rule' on the right-hand side top
For the trigger, select the option 'Field value changed'
Select the required fields under 'Fields to monitor for changes'
Click Save
Select 'New Action'
Select 'Edit issue'
From the Drop Down, select the third custom field
Click on 3 dots and select 'SET'
Add: {{issue.Consequence.value}}*{{issue.Probability.value}}
Click Save, Add the name of the rule and enable it

Please find below the snapshot for a similar rule.

Kindly accept the answer if this helps.

--GG

All comments

Fabio Racobaldo _Catworkx_

Hi @Chris ,

calculated custom fields is currently not an available feature on the cloud.

My suggestion is to try to put in place an automation and smart values (https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/)

Take a look here for similar question https://community.atlassian.com/t5/Jira-Software-questions/Automation-Average-calculation/qaq-p/2102128

Hope this helps,

Fabio

Frederik_l6tq22

Hi,

Isn't it possible for you to use a field (not custom) you don't use ?

I'm doing something similar with storypoint :

sum all the story points of issues in an epic when a value changes

" {{lookupIssues.Story points.sum}} "

and that value is edited into a custom field : calculated total SP

Vedant Kulkarni_Trundl

@Chris , you can try the JMWE addon which provides the functionality of event triggers using which you can calculate the field values.

Gaurav_0av1h6

Hello @Chris

As suggested in the Atlassian article, this can be achieved using Automation.

The steps to set up the Automation are as:

Go to Project Settings
From the left-hand menu, select Automation
Click on 'Create Rule' on the right-hand side top
For the trigger, select the option 'Field value changed'
Select the required fields under 'Fields to monitor for changes'
Click Save
Select 'New Action'
Select 'Edit issue'
From the Drop Down, select the third custom field
Click on 3 dots and select 'SET'
Add: {{issue.Consequence.value}}*{{issue.Probability.value}}
Click Save, Add the name of the rule and enable it

Please find below the snapshot for a similar rule.

Kindly accept the answer if this helps.

--GG

Bill Sheboy

Hi @Gaurav

I believe the mathematical operators are needed for that to work in a rule:

{{#=}}{{issue.Consequence.value}}*{{issue.Probability.value}}{{/}}

Kind regards,
Bill

Chris_cb7wvp

I'll give the automation a try and report back. Thanks for the input!

Chris_cb7wvp

The automation works! BTW I used the values offered by @Bill Sheboy in conjunction with the automation setup from @Gaurav .

Thanks all!

Gaurav_0av1h6

@Bill Sheboy absolutely right!1 We do need the operators.

Jonas Kopka

Stumbled over this in 2024 - the .value part is no longer needed (this actually made the automation not work)

Previous, not wokring query:

{{#=}} {{issue.Confidence.value}} * {{issue.Ease.value}} {{/}}

Working:

{{#=}} {{issue.Confidence}} * {{issue.Ease}} {{/}}

Thanks for the existing help!

Best,

Jonas

Bill Sheboy

Hi @Jonas Kopka -- Welcome to the Atlassian Community!

The Jira version (Cloud, Server, or Data Center) of automation, the field type, and the project type can impact when the value attribute is needed in rule math operations. For example, it appears some of the JPD fields may use the value as the default attribute rather than the selection id. My hypothesis for JPD is this is related to their calculated field handling in the views.

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud