Old name of a renamed custom field still being used in Field Configuration

Still need help?

The Atlassian Community is here for you.

Ask the community

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

  1. Shutdown JIRA instance
  2. Delete the contents of the JIRA Home Directory\plugins\.osgi-plugins directory
  3. Delete the contents of the JIRA Home Directory\plugins\.bundled-plugins directory
  4. Delete the contents of the JIRA Installation Directory\work directory
  5. Delete the contents of the JIRA Home Directory\caches\indexes directory
  6. Restart JIRA instance
  7. Perform re-indexing

     

Last modified on Feb 26, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.