How to use text (not JSON) entity properties in JQL?

[Yuriy Marchenko]

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!

[Nic Brough -Adaptavist- · Accepted solution]

Ok, let's go back to basics.

When you look at your Kanban board, what project(s) does it cover? 

Pick ONE of these projects, and start creating an issue from the Kanban board for that project.  Pick an issue type too.  List the fields you are offered.  Cancel the create (if you want), as we're just testing.

Now go to the SAME project.  Create a new issue using the standard UI option.  Make sure you select the same issue type.  List the fields you are offered.  (And cancel again if you want)

What is the difference between the two lists?

[Deleted user]

I found the difference.   Thanks for helping me!

I created a new user and he saw everything correct.   It seems I changed the configuration via Where is my field and he keeps on remembering it.

Greetz

[Steven F Behnke]

Can you screenshot the two examples of where you are entering issues to clear this up?

[Deleted user]

Thanks for the answer!

Where can I see it?  is it in Issue Detail View?  There I see a lot of fields?

[Nic Brough -Adaptavist-]

In the Kanban board settings.

[Deleted user]

I don't see a limit

[Deleted user]

I also see the same behaviour when starting in a different project without kanbanboard

[Nic Brough -Adaptavist-]

Does your board definition limit the fields on the Kanban board?