I’m trying to build a JQL function that lets users find issues that have comments with certain properties that aren’t currently stored in the comments index document.
I’ve been able to find plenty of examples in the Atlassian documentation and elsewhere on modifying the index document for an issue. Reading https://developer.atlassian.com/server/jira/platform/index-document-configuration/, I note that IssueProperty is the only available entity-key. Further, Jira doesn’t re-generate comment indexes on a background reindex, and tells customers that configuration changes shouldn’t require a full, stop-the-world reindex:
Is there an Atlassian-blessed means of updating the comment indexes? While I reckon it may be possible using Lucene’s API directly, I’d like to know if this is a bad idea for any reason before going down that road.