IsEmpty does not work on custom field

Michael Tai_98vev0

Step to reproduce.

1. Create a simple text custom field (my case is `Account holder's name`.

2. Add the custom field to a new Request type.

3. Create a Jira Automation triggered by this Request type.

4. In automation add a step to print the following comment

```

"{{issue.Account holder's name.value}}"

"{{not(issue.Account holder's name.value)}}"

"{{issue.Account holder's name.isEmpty}}"

"{{not(issue.Account holder's name.isEmpty)}}"

"{{issue.Account holder's name.value.isEmpty}}"

"{{issue.Account holder's name}}"

```

5. Raise a request ticket using the Request type created, don't fill in anything in your custom field.

6. Now you will get a comment

```

""

"true"

""

"true"

""

""

```

`IsEmpty` either returns null or true. It always returns' true' if I test it with `not(isEmpty)`. It is not correct. Am I doing sth wrong? I also tried `isNotEmpty`, but the result was the same, always `true` after `not`.

Kalyan Sattaluri_iinm1n

Hello @Michael Tai 

If Text 1 is your text field, then {{Text 1.isEmpty}} will give true/false based on if field has value.

Can you tell if {{issue.Account holder's name}} is returning value of the field? If it is not:

• Put a refetch action right after the trigger and rerun the rule. OR
• Instead of using field name {{Account holder's name}} , use its customfield value instead to try and log the value.

You need to be able to log the value successfully so you can evaluate if its empty or not.

Hope it helps and let me know if issues / concerns. Thanks!