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

Adding 2 custom fields together not working?

Ethan Bhardwaj

I've been trying to get 2 custom fields to be added together and comment the outcome in the comment section of the form. This is working when Customfield + 3.95 the output is adding them together and then commenting the correct output. However, we are trying to make the "3.95" a customer field that can be changed depending on what options are selected in the form, So we have changed the code the represent this with a custom field + custom field the outcome is being commented is just the input from the first custom field and the math s not being applied.

This code is working:

This code is not working

(Please note we have tried adding both custom fields with Issue.customfieldname and with the custom field ID and both are not added together correctly.

Further note:
here is the audit log of the automation, it shows as successful and that the equation is commented as written.

Accepted answers

Tim Kopperud

Hi @Ethan Bhardwaj, welcome to Atlassian community.

Are you able to provide images of

the math formula,
the two field values used. That means from an issue where the two fields contain values, but are not working?

Edited: I noticed later editions of the original question included this.

TimK

Bill Sheboy

Hi @Ethan Bhardwaj -- Welcome to the Atlassian Community!

In addition to the other suggestions offered...

I note your rule is editing an issue field before the attempt to add the comment. Is the comment referencing the field just edited and was that field empty before the edit?

If so, your rule is missing an action to Re-fetch the issue after the edit and before the comment:

...
action: Edit Issue field
action: Re-fetch Issue
action: Add comment
...

When a rule edits an issue, it is updating the data in the Cloud storage and is not updating the data as the rule proceeds. To refresh the data to the current state, add the Re-fetch Issue action to reload the issue before the rule proceeds.

Kind regards,
Bill

All comments

Ethan Bhardwaj

please read above.

Tim Kopperud

Hi @Ethan Bhardwaj, welcome to Atlassian community.

Are you able to provide images of

the math formula,
the two field values used. That means from an issue where the two fields contain values, but are not working?

Edited: I noticed later editions of the original question included this.

TimK

Tim Kopperud

@Ethan Bhardwaj, try small letters. customfield_xxxxx, not customField_xxxxx.

TimK.

Ethan Bhardwaj

Hi Tim,

thanks for the swift reply,

Currently, we have an automation that takes the "remaining balance" from an input field in the form and sets it to a custom number field
We then have another automation that has an If statement so depending on the input selected it will set the second field in this case "fee" to the appropriate number
We then have an automation that will add these custom fields together to comment on the final balance but this is where it is not working.

I hope this information can help.

Ethan

Ethan Bhardwaj

Hi Tim,

Unfortunately, the change in capitalisation hasn't affected the result.

Ethan

Ethan Bhardwaj

Hi @Tim Kopperud ,

Unfortunately, the change in capitalisation hasn't affected the result.

Ethan

Dick

Hi Ethan,

I have a similar calculation using custom fields.
My calculation has the issue reference in it:

{{#=}} {{issue.customfield_12800}} + {{issue.customfield_12805}} {{/}}

I suspect that if you only use {{customfield_xyz}} the value gets interpreted as a string.

Ethan Bhardwaj

Hi @Dick ,

Both the Custom fields are set as Custom Number fields so they shouldn't be Strings looking into the XML code of the form you can see that the fee is being set to the appropriate value and the remaining balance custom field is also the correct input.

So I am uncertain why when using {{#=}}{customfield_xxxx}} + {{customfield_xxxx}}{{/}} is not outputting in this case "27.95"

Dick

I suspect the variable you refer to gets the correct type ONLY if it's related to a full object (which the issue is).

I'm calculating the Weighted Shortest Job First (WSJF) using dropdowns and a calculation similar to the one I gave above.

Try it??

Dick

In your own examples, a full reference to the issue yields a correct value. Removing said reference doesn't work.

I really think the reference to the issue is important here.

Bill Sheboy

Hi @Ethan Bhardwaj -- Welcome to the Atlassian Community!

In addition to the other suggestions offered...

I note your rule is editing an issue field before the attempt to add the comment. Is the comment referencing the field just edited and was that field empty before the edit?

If so, your rule is missing an action to Re-fetch the issue after the edit and before the comment:

...
action: Edit Issue field
action: Re-fetch Issue
action: Add comment
...

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

jira

cloud

jira-cloud

math