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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Adding an Issue Property using Automation add-on and make it searchable using JQL

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?

1 answer

1 accepted

0 votes
Answer accepted
andreas Community Leader Apr 25, 2018

Hi Rian,

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

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.


If you have Script Runner, you can insert a raw XML module in Script Fragments. Would this combination potentially work?

I imagine this could change given Atlassian's acquisition.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

209 views 1 4
Join discussion

Community Events

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

Events near you