I'm using the Jira Workflow Toolbox to create a risk score by using 3 custom fields. I have the Risk Score getting set when it transitions from Create > Open just fine. Figuring that people might want to alter the Risk Score I setup the same configuration when going from Open > In Progress but I go to submit it I get the following: Error: null value at left hand side operand in arithmetic multiplication operation. Below is the configuration that I have for both transitions; Create > Open and Open > In Progress.
If the Ephemeral numbers are only used for the transition and I have it set Ephemeral number the second time then the value shouldn't be null. What am I missing?
Thanks for any help!
~jeff
Hello @Jeff Foege
Are you sure that there isn't any mistake in the configuration of transition Open > In Progress? Please, double check your configuration.
It's also possible that when you are transitioning Open > In Progress some of the fields "Risk Severity", "Risk Probability" or "Detectability" are not set.
I recommend you to set a default value in case of one of those fields are not set. To do it you can add an additional setting rule like this one:
(.*)1
For example, for setting Risk Severity you can use:
(Negligible)0.3
(Minor)0.5
(Moderate)1
(High)3
(Critical)5
(.*)1
This way, you are setting Moderate as default value for Risk Severity.
I know its setup correctly cause everything works when going from Create > Open and I used that configuration to setup the Open > In progress transition. The Risk Score gets set from Create > Open but if I try it again I get that null value error.
When I had those fields being set without doing the math step for the transition from Open > In progress it through an error.
I read something on an old site for this tool about adding [true]0 to the first place of the execution order. I'm just not sure what this means, the math step?
https://groups.google.com/forum/#!topic/jira-workflow-toolbox-plugin/DTOZ6tOomPA
If I can get this working then I would be done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HAHAHA. You were right I didn't have it configured correctly. When setting up the parse of one of the fields I had the source and target backwards. That certainly explains why the value was null.
Total user error. I just didn't see it until I started writing the values to the comments.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great news!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.