JIRA Obsolete custom fields are displayed when doing an issue search using JQL

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

  • When doing a JQL search for an issue, fields with the same name are displayed although one of them is obsolete and not used (see screenshot below).

Cause

  • A new custom field was created to replace an existing one which has the same name. The obsolete field has its Search Template set to Free Text Searcher instead of None.

Solution

  • Set the Search Template of the obsolete field to None.
  • Do a Background re-index during a non-busy period.

 

 

Last modified on Jul 19, 2017

Was this helpful?

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