Why a re-index after add-on license update?

I received a pop-up that indexing was required because of a add-on change. The only changes were update to licensing on:

Updated license key for Checklist (com.okapya.jira.checklist)
Updated license key for Essential Custom Fields for JIRA (com.primefieldsoftware.jira.essentialcustomfields)
Updated license key for Adaptavist ScriptRunner for JIRA (com.onresolve.jira.groovy.groovyrunner)
Updated license key for JIRA Misc Workflow Extensions (com.innovalog.jmwe.jira-misc-workflow-extensions)
Updated license key for Tempo Timesheets (is.origo.jira.tempo-plugin)
Updated license key for Announcer for JIRA (com.wittified.atl-announcer-jira)


However when I check the Instance Health it it reports the DB and the indexes are ok. Is this a bug or is a re-index required for license updates?

1 answer

With potentially invalid/expired license keys used, the addons may not fully work as part of their license checking policy.

As addons sometime provide custom fields with searchers or JQL functions or other components affecting indexing, it may be necessary to reindex once the license key has been updated. This will then allow addons to resume their full functionality and to work as they are supposed to.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

440 views 7 5
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you