Can we list all actions in JIRA that requires or triggers reindexing ?

[Vickey Palzor Lepcha]

Some that I can think of are ;

• Project Key change .
• New value added to an existing custom field .

[Nic Brough -Adaptavist-]

Actually, no, neither of those need you to re-index manually.

Behind the scenes, the index is essentially a copy of the issues in the database, in a very different shape, optimised for search.

There are three underlying things that mean you want to re-index an issue:

• Issue change (including create and delete)
• Structural configuration change
• Index corruption

Every time you amend an issue, it gets re-indexed, so in most cases (including change of project key), Jira re-indexes it automatically.

Structural configuration change is stuff like changing the context of a field (because that changes the shape of the index), upgrading (an upgrade has indexing built into it, but you can disable it, useful when you're going through a series of upgrades like 6.4 -> 7.0 -> 7.13 over a weekend), changing user directories, or migrating to a new machine.

Adding a new option to a field does not need a re-index.  All you're doing is adding an option to a list.  Until someone uses it, the index doesn't need anything more than a header record that it is there (which is a single record, and done when you add the option).  When people do use it, it's an issue change, so the index is built for it when you change the issue.

Index corruption is caused by system failures, bugs, or poorly written scripts or apps (things like people trying to put transitions on the current issue into post-functions)