Old name of a renamed custom field still being used in Field Configuration
Symptoms
Custom field defined called 'XXX' which has been in use previously. Renamed the field to 'YYY' and re-indexing was done.
However the Field Configuration that uses this field still sees it as 'XXX' and issues that previously had values for this field show the bame 'XXX'. However for new issues or issues that didn't previously supply a value for this field, they use the new name for the field 'YYY'.
Cause
Possibly JIRA is still storing the old cache of the custom field and that causes the old names to appear.
Resolution
- Shutdown JIRA instance
- Delete the contents of the JIRA Home Directory\plugins\.osgi-plugins directory
- Delete the contents of the JIRA Home Directory\plugins\.bundled-plugins directory
- Delete the contents of the JIRA Installation Directory\work directory
- Delete the contents of the JIRA Home Directory\caches\indexes directory
- Restart JIRA instance
Perform re-indexing