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 use text (not JSON) entity properties in JQL?

Hi everyone,


We've been using some entity (project, issue) properties, having text values in there worked perfectly fine, the conditions in the descriptor work fine, the REST API, etc.

Now the time has come to add a webhook for issue updates and we need to use the entity properties we have (with text inside, not JSON) to filter out once we don't care about.

The problem is the documentation explains how to index the properties with JSON values...

Does anyone happen to know how to index such fields or is there a way to use them for JQL search without indexing?

Any information helps, thank you!

2 answers

1 vote
Rhys Diab _Agile Docs_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Aug 08, 2020

I've encountered this problem too.

I resorted to saving everything that needs indexing in JSON. 

Not having to store these properties as JSON to use them in JQL searches would be helpful.

Thanks Rhys, it's good to know I'm not alone in this situation 🤗

@Yuriy Marchenko could you add an example of a property and an example of the king of JQL you're trying to use?


- Issue property (key: "com.railsware.SmartChecklist.checklists") with some text value e.g. "Hello, World!"

- Project property (key: "com.railsware.SmartChecklist.isDisabled") with "true" value


I can't find in the documentation how the JQL should look like so these are just guesses:

`[com.railsaware.SmartChecklist.checklists] is empty`

`com.railsaware.SmartChecklist.checklists is empty`

`[com.railsware.SmartChecklist.isDisabled] is empty`

I'm looking for issues of projects with blank/empty "com.railsware.SmartChecklist.isDisabled" property

@Yuriy Marchenko I think it will look something like this["com.railsaware.SmartChecklist.checklists"] is empty

I'm not sure about how it should be written between the ""

"com.railsware.SmartChecklist.checklists" is an Issue Property, we can ignore it, sorry for combining 2 examples.

The main goal is to find issues in projects that have "com.railsware.SmartChecklist.isDisabled" project-property empty or null, or not "true"

❌[com.railsware.SmartChecklist.isDisabled] is empty

❌[com.railsware.SmartChecklist.isDisabled] is null

❌[com.railsware.SmartChecklist.isDisabled].value is empty

I'd keep on guessing if I only knew it's possible :D 

Sorry for my mistake ...
I'm only guessing on my side too but I see that the "" are not in your last post.
Maybe something like this?["com.railsware.SmartChecklist"].isDisabled is empty

@Veronique DUFOUR Thanks for trying :)

Unfortunately, this is the very article I've mentioned in the question, it describes how to index for searching property with a JSON value, not text.

In the example, they got something like

  content: "Hello, World!"

as the "tasks" property value. 

If only I could easily migrate the property values we use from


to, say, 

{ value: "true" }

but I can't.

Using the REST API for such a migration will help, but I will use it only if I find no other way around.

Like Pavel Pavlovsky likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events