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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

How to check for empty Insight attribute in automation conditional logic

Charlie Misonne Community Leader May 24, 2022

In an edit issue action I'm setting the value of the Affected Services field. In a previous step I have an "lookup object" action.

My objects have an attribute called Service and sometimes this attribute is empty. In those case I do not want to include it in the edit action.


{"id":"{{Service.Service ID}}"}

So far I am unable to check for an empty attribute.

I tried several notations including these but it always results in TRUE.

  • {{#if(not(Service.equals("")))}}
  • {{#if(not(exists(Service)))}}
  • {{#if(not(Service.isEmpty))}}

2 answers

1 accepted

2 votes
Answer accepted

Hi @Charlie Misonne,

Would it work if you just excluded objects with empty Service attribute from the lookup action? Using the following IQL:

<your current IQL query> AND "Service" IS NOT empty

Hope this helps!

- Manon

Charlie Misonne Community Leader May 24, 2022

Simple and smart solution. Merci!

I still wonder why the conditional logic does not work but I won't spend any extra time on it.

Hello @Manon Soubies-Camy _Modus Create_ 

But I think when you have a scenario with many objects attributes, and someones of them are empty and others not empty. So in this case, you can't remove the object in the IQL, because this will remove the object with all attributes - the empties and not empties. In others words, I need a solution to be handled one by one attribute. Did you get my point?

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events