Jira Automation with weighted average calculation.

[Akeem Ibrahim]

Hello Everyone,

I have problem creating an issue with weighted percentage, if anyone can help. i have the following issues to be configure to resolve IT solution:

1. Business Important                40%

 drop down:  (i) contribution 40%   (ii) roadmap  20%   (iii) cost  30%  (iv) future 10%.

2. Risk & Regulatory aspect   38%

  drop down : (i) compliant 40%   (ii) situation 25%   (iii) services 20%    (iv) security 35%

3.         Potential                  22%

drop down:  (i) Long term 30%   (ii) Short term 25%  (iii) new future 28%  (iv) unforseen 17%.

From the main issue category (1, 2, & 3) it sum up to 100%. Then all the subtask % value sum up to parent or linked issue 100%. I want overall  weighted to have following criterial which are:

1 - >80%

2- 50% - 79%

3- 20% - 49%

4- 0 - 19%.

I need help on how to include the value of percentage into the automation rule, or condition in the automation of the project settings.

Please kindly help.

[Bill Sheboy · Accepted solution]

Hi @Akeem Ibrahim 

It is likely this is possible using the math expressions for rules: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/

Some things to note for such a rule:

• consider what to do when any of the fields needed are empty
• consider under what conditions you want the values examined updated (e.g., issue create, issue field updates, change of parent, change of status, etc.)
• investigate the new lookup tables feature of rules as that may help with calculations: https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333

Writing automation rules requires learning and experimentation.  I recommend trying to create your rule and test that it does what you want.  If it does not, post images of the complete rule and audit log details, and describe what does not work as you expect.  That information will provide context for the community to offer suggestions.

Kind regards,
Bill

[Akeem Ibrahim]

Thank you, I will give it a go.

[Akeem Ibrahim]

{{issue.Story Points.asPercentage}}

i have tried, but i could not get it. The Automation does not perform any actions, as its stated in the green text "NO ACTIONS PERFORMED". If anyone can help, i used the smart value on Jira, maybe i am wrong in expression.

Please help!!!!

[Bill Sheboy]

It appears the first condition is failing, and so I wonder if you have the correct smart values for your fields.

Smart values are name, spacing, and case-sensitive.  Please try using the how-to article below to confirm the smart values in your rule.  Basically you identify an example issue with your fields, call the REST API with a browser, and then search for your fields to find their exact smart values.  You may also use the custom field id value for the fields.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Audrey Tolman]

I have the same situation in Product Discovery.  I created a custom field to aid in WSJF calculation from a business perspective that feeds into the overall WSJF calculation (we call this BizJF).  The custom field contains multiple questions.  Each question has a dropdown list to select from.  Each answer is weighted.  I've tried reformatting my existing formula to match the format I have found online, but I keep getting an invalid expression error.  Any suggestions?

[Bill Sheboy]

Hi @Audrey Tolman -- Welcome to the Atlassian Community!

First thing...your question seems related to this thread, but by posting it here only the people following this one will see it.  Please consider creating a new question, and linking to related ones.  Then those following newer posts will see it rapidly.  Thanks!

For a question like this, please post images of your complete rule, including the details of your formula calculations, and of the audit log details showing the rule execution.  Those will provide context for the community to offer suggestions.

Until we see those images...

I suspect the problem is when you are using the dropdown fields in the calculations, something is missing.  Often when using a numeric value in a dropdown like for WSJF-like calculations, the value is this:

{{issue.myFieldName.value}}

Another possibility is you have an incorrect smart value for your field.  Smart values are name, spacing, and case sensitive, and may not look exactly like the field on the screen.  You can check that with the how-to article below.  Essentially you find an example issue (i.e., your idea) with the field, call a REST API function with a browser, and then search for your field on the page to learn the correct smart value.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill