Epics displaying as unlabeled in Jira server
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
There are epics in your Scrum and Kanban Boards that appear unlabelled.
Cause
Jira has not been re-indexed after installing Jira Software.
Epic tickets were created before the Jira Agile 6.1+ was created. In Jira Agile 6.1+ there is a new custom field named Epic Name which is used to store the name displayed in Jira Agile.
Issue type Epic is not available within Epic Name custom field context.
Epic custom fields have missing customfieldsearcherkey
The project(s) and Epics have been imported from a Jira Cloud Environment. In Jira Cloud the Epic Name field is optional and, therefore may not contain a value.
Resolution
First, check the following:
Jira was re-indexed after Jira Software was installed. If it was not, or you're uncertain, re-index Jira.
Verify if the Epic issue type is available within Epic Namecustom field context.
Verify the epic fields are not affected by missing customfieldsearcherkey
If the above does not resolve the problem, there are known two ways to change the epic name.
Click the three dots on the right side of the epic and choose Edit Name
Open the Issue detail view of the epic ticket and choose edit on the ticket. You should be presented with an option to change the Epic Name there.
Was this helpful?