We have a custom field that checks to see if a user has logged work on any issues in the last N days. The field uses the worklogged issue function and returns the number of issues that have work logged on them. We then run a query to find all users whose value for this field is 0. When work logs are recorded, the custom field returns the correct updated value, but the search index is not updated, so the query returns the old value.
Running full re-index manually fixes the issues, but we will need an automated solution.
What would be the best way to trigger a re-index of the custom field's value so search results work correctly?
Using JIRA 6.3.5 and ScriptRunner 3.0.5
Using the script-runner, add a simple listener to catch "work logged", "work log updated", "work log deleted" etc events. It can then re-index the appropriate issue. (Work log moved to another issue is a bit more of a pain as you'd need to index both)
Your question only makes sense if you're using a custom field to record work logs on linked issues. If it's the current issue, it will get reindexed when a work log is added.
There is an example of reindexing linked issues using an event handler here: https://scriptrunner.adaptavist.com/latest/jira/recipes/scriptfields/workRemainingInLinkedIssues.html#_indexing (but read the section above too).
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs