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

Automation rule to multiply one custom field by story point field

Leena K_g7r3yc

Good day,

I have read most of the posts on how to create an automation rule to multiply story point field by another custom field(progress percentage), and store the result in a third custom field (completion)but nothing worked till now.

the objective is to multiply two fields and store the result in another custom field.

I’m using JIRA cloud version.

can somebody please provide a step by step instructions on how to achieve that?

Thanks,

Accepted answers

All comments

Stevan Mandić

Automation:

1. Trigger: choose your trigger

2.action: Edit issue:

Edit field: Completion

Value: {{#=}}{{issue.customfield_XXXXX}} * {{issue.Story Points}} {{/}}

Replace XXXXX with your Progress Percentage custom field ID.

You can find custom field IDs if you type in your browser:

YourJiraInstance.atlassian.net/rest/api/latest/field

Both fields that are being multiplied have to be NUMBER fields.

Bill Sheboy

Hi @Leena K -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

If you have not started a rule yet, I recommend trying to do so. Successfully using automation rules requires learning and experimentation. When one uses rules provided by others without understanding them, it is unlikely they will be able to maintain or improve them.

To get you started on creating your rule, please refer to these documentation and example sources:

Kind regards,
Bill

Leena K_g7r3yc

Thanks Stevan ..., this worked.

Leena K_g7r3yc

@Stevan Mandić do you know how can I create a field to sum the values of (Completion) field that was calculated in the previous step.

Sum = total (Completion) --> for every single (Issue, Task ...) in the project.

Leena K_g7r3yc

@Stevan Mandić do you know how can I calculate the Sum of (Calculation) field that was calculated in the previous step.

Sum = total (Calculation) --> (for every single issue, task, ... etc) in the project.

Leena K_g7r3yc

This is what I have done, but this is scheduled every 6 min, I couldn't test it yet, I need to wait 6 minutes, do you know how can I make it run every 1 min? maybe i need to work on the JQL query, but i dont know how to do that

Screenshot 2024-05-19 122041.png

Stevan Mandić

@Leena K In the previous comment I have explained you how to multiply two number fields

But....

What is the purpose of those calculation?

1) why do you multiply Progress Percentage by Story Points (how do you get Progress Percentage value? What does that value mean? Also, you should not multiply story points with any field since story points are relative estimations.

2) on what level do you need a Sum of all issues (calculation fields)? Project level?

What will that sum value tell you exactly?

Leena K_g7r3yc

my answer to point number 1 is that we are experimenting with this, if it works, we will think more about the math.

the answer to point two is yes on a project level.

Stevan Mandić

1) I strongly suggest you not to combine time/day(progress) estimations with story points (multiplication of those fields doesn't make sense)

2) you cannot sum up all values on project level.

But:

What you can do is to sum up all calculation field values on Epic level.

Screenshot 2024-05-19 at 13.02.06.png

(Just replace customfield_id with your Calculation field Id, and also: put JQL condition "type!=epic" after trigger).

This rule says: when the value of calculation field changes for any issue, for parent Epic calculate the sum of all child Calculation fields and update Calculation field of the Epic.

If you are using Jira Premium and you have hierarchy level above the Epic, for instance: "Initiative", you could then create another rule which will update Initiative Calculation field when epic calculation field is changed (instead of "epicLink""and "Epic Parent" you will use Parent - both in branching and JQL). Also, put JqL condition "Type=epic" after the trigger.

important: for both these rules you should mark the checkbox: Allow rule trigger- Check to allow other rule actions to trigger this rule since these rules depend on the automation rule that updates Calculation field on single issue.

Leena K_g7r3yc

I followed the steps you mentioned above and stayed away from story points (it make sense).

But the automation didn't work, and I'm not getting any error in the audit log, so can't identify why it's not working.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud