Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation Rule to null check custom field


I have a custom field field in Jira that can look like this:

"customfield_10130": [
"self": "https://<jira>/jira/rest/api/2/customFieldOption/10251",
"value": "Yes",
"id": "10251"

When this value is not set, it looks like this:

"customfield_10130": null

I'm trying to compare this custom field when it's null, and cannot ever get any type of information from it. I've used all sorts of smart values - both what I've found in the documentation, and guessed at, they include:

  • {{issue.customfield_10130.isEmpty()}}
  • {{issue.customfield_10130.length()}}
  • {{issue.customfield_10130.size}}
  • {{issue.customfield_10130.isNull()}}
  • {{issue.customfield_10130 = null}}

None of these provide anything I can use in a comparison. Any ideas how to compare this empty/null custom field?

5 answers

I've had success using an "Advanced compare condition" too like this.


In my example here, I'm checking the {{issue.timespent}} smart value for null.

Couldn't believe it - but works. Incredible...

I still didn't get anything being able to detect null value in automation.

The does not equal or not matching, is always true no matter what is the value set, not set or set to None for custom field drop down.

Is someone have a solution for a drop down custom field?



I'm using Advanced compare condition with regular expressions. For the below example I check if a field from the issue's epic is not empty.

Screenshot 2021-03-11 at 20.10.03.png

For your case would be a similar check

Screenshot 2021-03-11 at 20.11.16.png

0 votes

Hi @mnd , 

Tried using the "Advanced compare condition"? 


@Tom Williams thanks for the response! (Apologies for my delayed response). When I tested this, the "if" check always passes, regardless of whether the field is actually empty or not.

@mnd - strange this works for me in my rules. You could use the log action to capture what the rule is picking up when you expect it to be empty. 

I get the same thing as @mnd. I'm using a custom date field which might be the issue. All I want to do is set the date to today if it hasn't already been set. Why does this have to be so difficult.

I just tried this with a JQL check as well "Being Developed Date[Time stamp]" is EMPTY and when I test the JQL it tests just fine but when it comes to actually working, I just get this in the log `The following issues did not match the condition:`

After walking away from this and taking a breath. I realized I just had the if check in the wrong place. I was able to get it working with the jql check. YAY!!!!

do you have a screen shoot? I can't make it work.


0 votes
Hana Kučerová Community Leader Nov 14, 2020

Hi @mnd ,

would you please provide us more information - how does your automation rule like (triggers, conditions, actions - what do you need to do, if your custom field is empty or not empty...)?

Is it server or cloud verion of automation for Jira?

Thank you.

Hi @Hana Kučerová, thanks for the response. I'll try to explain it more thoroughly below.

Just for more context, this is related to another question I posted - trying to understand either situation to come to a solution. The other question is posted here.

I'm demonstrating the behavior in two automation rules - but hoping there is a better way, which combines them into a single rule.

In this project there is a sub-task called "Release Notes". There is also a custom field called "Primary QA" that exists on both the Release Note sub-task, and the parent issue. I would like to make sure that the "Primary QA" value of the parent is always in-sync with the "Primary QA" field in the "Release Notes" sub-task. These are the two scenarios I'm trying to make work.

  1. When the "Primary QA" field is changed in the parent issue, the change is reflected in any existing "Release Notes" sub-tasks. (Currently working with the "Field Sync: Primary QA" automation rule below)
  2. When a "Release Note" sub-task is created for the parent issue, the new sub-task's "Primary QA" matches what is in the parent issue. (Currently working in "Field Sync: Primary QA 2" automation rule. Attempted as the second branch chain in "Field Sync: Primary QA" automation rule).

It seems I can trigger on when a field is changed, or an issue is created, but if I could trigger on both states, then it seems like I could work through the logic in the automation rule.

Any suggestions would be appreciated. Thanks for your time!


Field Sync - Primary QA 1.pngField Sync - Primary QA 2.png

Hana Kučerová Community Leader Nov 16, 2020

Hi @mnd ,

thank you for the clarification. I've posted the answer to your other question.

The only information I'm missing is, why do you need such comparison?

Is customfield_10130 your Primary QA custom field?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

3,108 views 10 9
Read article

Atlassian Community Events