How to get a numerical value from a text string to automatically sum together in a separate custom f

[Wesley April]

Ive created several custom fields that have text values as their answers. Id like to write an automation rule(s) that take those inputs and make them assigned numerical values which sum together in a separate custom field on the same screen. The value of these added fields then determines the issues type's priority level. 

Example:

How many customer's impacted?

- all (automatically enters a value of 10)

- some (automatically enters a value of 5)

- none (automatically enters a value of 0)

Customer severity

- Stoppage (automatically enters a value of 10)

- Inconvenience (automatically enters a value of 5)

- No Impact (automatically enters a value of 0)

If I selected "all" and then "inconvenience"; my total would be (15)

[Trudy Claspill]

Hello @Wesley April 

Yes, this is possible.

Have you done any work to try to construct this rule? If so, please show us what you have so far.

[Wesley April]

This is for just one sequence. Basically saying when field "x" is given an input; take said input and edit this other field with the numerical value based on the question's answer. Main problem Im having is when I try to add in the same logic more times for each of my other questions. I cant seem to get the numerical values to add up and give me a total value which I can then use to determine the priority level. 

[Trudy Claspill]

How many of these selection list fields do you have that you need to evaluate? Is it just two, like in your example, or are there more?

How many value options are there for each of these fields?

Is it possible for the value selected in one of these fields to be changed after it is initially set? If so, would the calculated value need to be updated to align with that change?

There are a couple of different ways to go about this, but selecting the best one will depend on your answers.

[Wesley April]

7 total fields
5 of them have 4 available selections
1 has 2 available selections
1 has 5 available selections

I would like the calculated value to change if an answer is changed, yes. 

[Wesley April]

• How many customers?
  
  • All (15)
  • Many (10)
  • One (5)
  • None (0)
• How many Technologies?
  • All (15)
  • Many (10)
  • One (5)
  • None (0)
• How many capabilities?
  • All (16)
  • A,B, or C (3 points per - possible max of 9, possible min of 0)
  • D (2)
  • E, F (1 point per - possible max of 2, possible min of 0)
• Customer Impact Level?
  • Work Stoppage (15)
  • Work Inconvenience (10)
  • Minor Work Inconvenience (5)
  • NO Impact (0)
• Business Impact Level?
  • Work Stoppage (15)
  • Work Inconvenience (10)
  • Minor Work Inconvenience (5)
  • NO Impact (0)
• Reported by Customer?
  • Yes (20)
  • No (0)
• Time Severity?
  • 10-12 Weeks (4)
  • 7-9 Weeks (3)
  • 5-6 Weeks (2)
  • 2-4 Weeks (1)
  • 0-1 Week (0)

[Trudy Claspill]

That is a lot of fields!

Are these all single selection lists, or are any of them multiple selection lists?

I'm going to spend a bit of time thinking about this and then I'll get back to you.

I don't think you would be able to do this with one rule. There are too many components that would need to be created to look at each of the fields and determine the value for each of the corresponding selections. You might run into the limit of 65 components in a single rule.

My initial thought is to have a companion number field for each of these selection list fields. You would have a rule for each selection list to set the companion number field. You might be able to condense that into a smaller number of rules, each handling a couple of fields. Then you would have a rule to detect changes on the companion number fields, and sum those values up to update the "priority level" field. But there may be a more efficient method.

Would you consider updating the values displayed in the fields to explicitly include their numeric value? i.e. "Work Stoppage (15)"

Also, are you open to third party apps for a solution?

[Wesley April]

These are all single select lists. 

I expected that it would take more than 1 rule but I wasnt sure how to go about that. 

Im also weary about including the numbers in the list selections because people could then "game" the system and make their issue have more weight than it actually does. 

Im open to add-on so long as it doesnt cost an arm and a leg. 

[Wesley April]

Any ideas @Trudy Claspill ? Im at a complete stand still on this. Thanks for your help thus far

[Trudy Claspill]

I have not had time to give more thought to this problem since last I posted.