I was adding some Issue properties using the Automation add-on that we will use for other automation rules, etc. But we also want to search on these issue properties using the JQL construct issue.propery["ISSUEPROPERTY"].ATTRIBUTE to surface particular issues in Service Desk Queues.
It seems like the issue properties that I create are not indexed by JIRA. I've done some searching and it appears that issue properties that are added by plugins can be made indexed by editing the jiraEntityProperties definition. But because these were created by this plugin, I'm not sure there's a way to make these indexed.
Is there a way to force these to get indexed?
Yes you're correct that entity properties added through our 'Set entity property' action aren't indexed. As you mentioned this would require an entry in either the atlassian-plugin.xml (in server) or in the atlassian-connect descriptor in cloud (see https://developer.atlassian.com/server/jira/platform/entity-properties/#how-do-i-make-the-properties-of-an-entity-searchable)
These entries are static though (meaning the add-on has to be re-installed anytime it changes) and I don't believe there's a way to mark issue properties to be indexed through a 'dynamic' API currently. So in this case there's not much we can do unfortunately. We can't trigger an add-on re-installation anytime a 'Set entity property' action is added and we couldn't even update the atlassian-plugin.xml descriptor dynamically anyways.
Sorry, but in this case we're bound by Jira's API limitations.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events