With Jira 7 we indexed references to issues in the following way: {id: [1, 2, 3]} in issue properties. And we then had a indexing configuration like this: <index-document-configuration entity-key="IssueProperty" key="atlas-crm-issue-entity-property"> <key property-key="atlas_crm_entit…

You’re probably not going to like this but Atlassian doesn’t support array types on Issue Properties. Entity properties How to format Jira entity properties such that they are searchable via JQL - #5 by tbinna Making entity property searchable

You are right I dont like this :joy: This has been supported on Cloud for more than 2 years now. That is why we thought it would work the same on server. But we actually managed to fix it by saving it in a string like this: "1 2 3" and then index as text. It wil tokenize it on the spaces and then y…

Sorry and good luck :frowning: That’s a super nifty solution though. Thanks for the follow up.

@m.kuijpers I am running into the same issue but I have not seen anywhere stated that arrays are not supported on Jira Server. The documentation on entity properties for Jira Cloud and Jira Server (if arrays are supported) is super confusing ( for reasons given here ) and I have reported it to Atlass…

https://developer.atlassian.com/server/jira/platform/index-document-configuration/ Currently, specifying indexes for JSON arrays is not supported.

This seems to be a regression since this was working in Jira 7, but not 8. Consequently, I have created JRASERVER-72078 for the Jira Server team to address.

Indexing an array in issue entity properties is broken on jira 8

Jira Development Jira Server

sfbehnke March 14, 2019, 11:50pm 2

You’re probably not going to like this but Atlassian doesn’t support array types on Issue Properties.

Entity properties
How to format Jira entity properties such that they are searchable via JQL - #5 by tbinna
Making entity property searchable