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; } } }

Expression in a calculated field

Арина_4ok4he

Hello!

I need to calculate the percentage of related issues of a certain type and status to the total number of related issues of the same type. And then display the value in the calculated field.

To do this, I need to create an expression in a calculated field, but I don’t understand how to do this at all.

The formula should look like this:

Number of related tasks with a certain issuetype and status / total number of related tasks with this particular issuetype * 100

Help me please

Accepted answers

Арина_4ok4he

@Dick

Thanks, but for me it’s more priority to configure this through an expression rather than through automation

All comments

Dick

Hi Arina,

You can use an automation to do the math for you.

the lookup issues can be referenced using .size as is given in the Atlassian documentation

Арина_4ok4he

@Dick

Thanks, but for me it’s more priority to configure this through an expression rather than through automation

Dick

The expression would fill the custom field using automation.

It would kick-off your calculation and saving the result, keeping it up-to-date for you to enjoy...

more documentation on math expressions available in automation

Dick

It's the automation that would gather two arrays of issues that are described in your formula, then using the .size operator you can construct the equation and store the outcome in a similar manner to this:

edit issue

customfield

Bill Sheboy

What is the source of information for the expression you show? A rule may only have one Lookup Issues result at a time, so the above expression cannot work.

Instead a single lookup issue might be used with smart value, list filtering and a math expression, or repeated lookups could save intermediate results in created variables or with a lookup table. All of these depend upon which version of Jira (and automation rules) is used, and that information was not provided by the original poster.