Why is there no value after Automation rule ran successfully

Bola Oye

1. I Created two Custom fields

2. Custom Field A (customfield_15063) is processed and it generated a value 178.43

3. Custom Field B is to take this value (178.43) and Multiply by Number of days e.g. 4  

4. Output of step 3 is always going to be divided by 5.

What step am I missing?

{{#=}} Round({{issue.customfield_15063).multiply(issue.Number of Days in Office.divide(5))}},2) {{/}}

 

 

Bill Sheboy

Hi @Bola Oye 

For a question like this, context is important for the community to help.  Please post the following:

• what version of Jira are you using: Cloud, Server, or Data Center
• for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

First, have you confirmed the smart values / custom field IDs for your fields?  Smart values are name, spacing, and case-sensitive.  When an incorrect one is used, that often fails with no errors.

Please use this how-to article to confirm your field smart values / custom field ID values: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

 

Next, you have some stray characters in the smart value expression you show.  And as it mixes inline and long-format math expressions, it may not work as expected.  Perhaps try this, assuming the smart values and custom field IDs are correct:

{{#=}} ROUND( {{issue.customfield_15063}} * {{issue.Number of Days in Office}} / 5, 2 ) {{/}}

 

Finally, based on what you describe, I wonder if you are modifying those custom fields in the same rule where the math expression is attempted.  If so, it is likely the rule is missing a Re-fetch Issue action to reload the data before the steps proceed.  For example:

• action: edit issue, changing one (or both) of the custom fields
• action: re-fetch issue
• action: edit issue, with the math expression using the updated fields
• ...

 

Kind regards,
Bill