Access Issue Properties through JQL

[Rebekka Heilmann _viadee_]

I am setting Issue Properties through Jira Automation and want to query these properties through JQL. What is the correct syntax for that?

I've tried

issue.property[testprop] is not empty

issue.property[testprop].value is not empty

and it's not working.

I have a few ideas of why that is:

• This question from 2018 suggests that properties added through Automation are not indexed. Maybe that's still the case?
• I am not setting the property correctly and it needs a different format

Note/context: I am trying out properties as alternative to saving values into hidden fields. I need to memorize the number of reminders sent out to a user and used a field for that purpose. That has stopped working and the field now needs to be added to the screen, unless you use the A4J user as actor.

[Pablo V_ · Accepted solution]

Hi @Rebekka Heilmann _viadee_ 

As I understand it (please anyone from the community correct me if I'm wrong), the JQL syntax isn't the real problem. Jira Automation’s Set entity property action stores the property, but it does not automatically register that property for JQL indexing.

I think Jira only makes an entity-property value searchable after an app (Connect- or Forge-designed) declares the property. This is mentioned at https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/#making-searchable-entity-properties

Sorry to bring the bad news. Someone closer to Atlassian's engineering teams can probably provide further help.

Have a great day!

- Pablo / ServiceRocket SSE

[Rebekka Heilmann _viadee_]

Still the same issue as reported in 2018 then. Thanks for confirming!

[Gor Greyan · Accepted solution]

Hi @Rebekka Heilmann _viadee_

I don't believe the JQL syntax is the problem here.

The Set entity property action in Automation stores the property on the issue, but that doesn't automatically make it searchable via JQL. For an entity property to be queried with issue. property[...], it first needs to be indexed by an app (for example, using a Forge or Connect jira:entityProperty module)

https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties

Out of curiosity, have you verified that the property is being written successfully by retrieving it via the REST API (GET /rest/api/3/issue/{issueKey}/properties/testprop)? If the property exists there, then the remaining limitation is most likely the lack of JQL indexing rather than the query syntax itself.

[Rebekka Heilmann _viadee_]

Still the same issue as reported in 2018 then. Thanks for confirming!

Nah, not tried that as i hoped the issue was elsewhere. Not going to add Web requests to a simple Automation in this case so will go a different route than issue properties then.