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

Aggregate values with Issue Creation Trigger

Adam Rosenbaum_0ce6b3

I have a form with several questions. Each question will be point weighted. When I hit save and the issue is created I want to aggregate the value assigned to the choice in each dropdown box without having to create if/then/else statement for many different combinations. I am not of JIRA capabilities, bit I have 2 thoughts on how to accomplish, if JIRA allows:

1. create an automation rule for a field that aggregates each box. I.E create a field called Points and the equation would be Points=Points + (Field 1 Value, Field 2 Value) etc.

2. assign a numerical value to each choice in a dropdown list and write an automation rule that adds the value of each field.

I will that I am not an expert in coding so if JSM offers this functionality, that is preferable.

Accepted answers

Jack Brickey

Hi @Adam Rosenbaum , welcome to the community.

Let me first state that I have not attempted such a solution previously. However, you may be able to achieve this using automation. Here are my thoughts on an approach.

you could define/name each drop down such that it includes the weighting. For example, option1 (15), option2 (5), etc.
you could use Regex to parse/extract the weighting. Here is a good article that might explain this for you - Extract-Content-out-of-Description-and-Summary-with-Regex . NOTE: I am unsure if Regex will work on a non-text based field. I need to play with that to see.
use Automation variables to temporarily store each field's selected weighting. Which is extracted using the Aforementioned Regex method. Here is an article on using variables - jira-automation-actions look for the section on Create variable.
Create a custom number field for the total weighting where you can place the aggregated value. You would use an Edit issue action and add all of your created variables using Automation's math function - Jira-smart-values-math-expressions

granted, the above is not a full solution for you, but a concept of what I would attempt. Hopefully someone who has actually done something similar to this will chime in and provide greater detail. If you do attempt the above, please keep me posted with your progress, and I will do what I can to assist.

Adam Rosenbaum_0ce6b3

so if i am understanding Jira's functionality correctly, the variable cannot be created ahead of time and assigned a value after the fact, the variable needs to be baked into the ITE statement.

If the field is not empty and contains choice 1 then create the variable and assign a point value of 10, else if the field is not empty and contains choice 2 then create the variable and assign a value of 20...so on until all choice are accounted for. Then 1 more automation rule that simply aggregates the value of every variable that has been created and there is the number I am looking to get.

Adam Rosenbaum_0ce6b3

I found the table Creation as an action after the trigger is invoked. So in theory:
Upon submitting a form (Issue creation trigger) the tables are created
The values are extracted and edit fields action will aggregate those values

Do the tables need to be created every time, or is there a way to create a standalone automation rule that creates the tables?

All comments

Jack Brickey

Hi @Adam Rosenbaum , welcome to the community.

Let me first state that I have not attempted such a solution previously. However, you may be able to achieve this using automation. Here are my thoughts on an approach.

you could define/name each drop down such that it includes the weighting. For example, option1 (15), option2 (5), etc.
you could use Regex to parse/extract the weighting. Here is a good article that might explain this for you - Extract-Content-out-of-Description-and-Summary-with-Regex . NOTE: I am unsure if Regex will work on a non-text based field. I need to play with that to see.
use Automation variables to temporarily store each field's selected weighting. Which is extracted using the Aforementioned Regex method. Here is an article on using variables - jira-automation-actions look for the section on Create variable.
Create a custom number field for the total weighting where you can place the aggregated value. You would use an Edit issue action and add all of your created variables using Automation's math function - Jira-smart-values-math-expressions

Jack Brickey

Hi @Adam Rosenbaum , I was playing around with this concept a bit and determined that it might be better to simply use the "split" function within automation. Below is an example of this in action. Basically, you would leverage the field value naming convention I mentioned previously but instead use a dash as the parentheses I believe it's a reserve character will not work.

in this example I referenced my Change reason field where I had one value listed as Failure - 7. The below automation properly extracted the 7 and placed it into my variable which I then used within a comment action simply to test. Oh, and the Log action was just part of my test as well but useful when creating automations.

Adam Rosenbaum_0ce6b3

But I would have to create a variable for each field and use the Edit Issue function to sum all the fields? Lastly, there is no way to hide the number after the "-" I assume.

Can I write automation that creates an empty variable, and assigns a number to it based on the selection. So:

create variable {{CRText}}

If Field 1 = then CRText = 10

Else if Field 1 = B then CRText = 20

Finally, one more automated rule that uses Edit Issue to aggregate all variables.

What do you think?

Jack Brickey

Hi Adam,

But I would have to create a variable for each field and use the Edit Issue function to sum all the fields? --- A: Yes

Can I write automation that creates an empty variable, and assigns a number to it based on the selection. --- A: I don't understand. If you look at the documentation or try to create a variable you will see that you must define the value. As mentioned above, you can use smartvalues for this.

based on your original post, I assumed your goal was to sum up the weighted issues from several different fields that were filled in by the customer. You indicated you wanted to avoid large if then else scenarios so I attempted to present some ideas based on what I thought you were requesting. I suggested the variable approach so as to avoid creating unnecessary custom fields to capture the individual field weighted values.

I think the best course of action is for you to take a stab at creating a rule and playing with the various components to see if you can zero in on what might work best for you.

Adam Rosenbaum_0ce6b3

so if i am understanding Jira's functionality correctly, the variable cannot be created ahead of time and assigned a value after the fact, the variable needs to be baked into the ITE statement.

Adam Rosenbaum_0ce6b3

reading over that now. I'll let you know if I have anymore ????

Thank you both

Adam Rosenbaum_0ce6b3

Do the tables need to be created every time, or is there a way to create a standalone automation rule that creates the tables?

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-service-management-cloud

jira-service-management