Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Custom Field Value Is Always Blank

Michael December 15, 2020

I have created a rule that will update a custom field based on the description. This successfully works, but when I try to include the value of the custom field it is always blank. I have two rules, one to update the custom field and another rule that will trigger an email. I thought because they are two different rules that it was the problem, but I created a test rule to update the customer field and then log the value of the custom field. It always returns empty.

Here is how I tried logging the value:

  • {{issue.fields.customfield_13141}}
  • {{issue.fields.customfield_13141.value}}
  • {{customfield_13141.value}}

My rule:

  • When: Issue created
    • For Current issue
      • Description contains
        • Severity: Critical
      • Then: Edit issue fields
        • Severity
      • And: Add value to the audit log.
        • {{issue.fields.customfield_13141}} {{issue.fields.customfield_13141.value}} {{customfield_13141.value}}

1 answer

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 15, 2020

Hi @Michael 

Is the custom field you are trying to log the same field that you just modified within the rule?

If so, I believe it is logging the original value (at the point of trigger), not what you changed.  Please try adding a Re-fetch action after the edit and before the logging.  That reloads the issue into the rule context before proceeding.

Best regards,


Mahmud Abdu September 21, 2023

Thanks this helped me too

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events