Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Using select field option weights in automation

Caitlyn C
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 8, 2026

Goal: To calculate an overall priority score, where the calculation of the score varies based on the value of a category and the inputs to the score are several (e.g. 4) select fields with number-based option weights. 

Context: Since I can't use conditionals (if category == 'a') in the write your own expression of a custom formula field, I am now using automation for checking the category and calculating the scores in varied ways based on the category. Additional context: the output field or score is a number field, since I suspect a formula would be overwritten by frontend calculations. I'm trying to find a solution that uses the option weights defined by users on the frontend rather than hardcoding weights in the backend automation.

Problem & Ask: I have been unable to access the select fields' number-based option weights in automation. I can get the select option value (e.g. 'High', 'Medium', 'Low'), but the weight assigned to it (e.g. 30, 20, 10) has been difficult to access. Are these stored in the backend, and if so, how might you access the number-based (or rating-based) option weight of a select field in automation?

Steps taken: I've tried logging several variations of the fields themselves or the formulas: {{select1}}, {{select1.value}}, {{select1.optionWeight}}, {{select1.value.optionWeight}}, {{select1.weight}}. I've also tried with and without math, {{#=}}{{/}}. The log will show "High" or "High + High + High + High" for some variations, but it has not returned the option weight 30 nor the score 120. Just to show an example, I've included a simple addition below. I've used both fieldnames (select1, select2, etc.) and field IDs (customfield_11111, customfield_22222); both work to retrieve the select options but not the respective number-based option weights.

Example: 

{

"fields":{

"score": {{customfield_11111}} + {{customfield_22222}} + {{customfield_33333}} + {{customfield_44444}} 

}

}

1 answer

0 votes
Walter Buggenhout
Community Champion
August 8, 2026

Hi @Caitlyn C and welcome to the Community!

Before diving into the tunnel you're already in with you, may I suggest to take a step back? The option weights in JPD are designed to be used in JPD formula fields. If you say you want have limitations there (the additional conditions you want to apply) and for that reason would like to use automation instead, you might want to consider moving the numerical logic into automation as well.

In automation you can create a lookup table where you map the values from (standard) fields to numerical values that your can then leverage in your calculations.

A fellow champion wrote a community article explaining how to set this up. That might be a feasible workaround for what you are trying to achieve.

Hope this helps! 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events