Missing options for "Epic Status" after Jira installation
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
Summary
This article covers why the "Epic Status" fields shows no options after a fresh Jira installation.
Environment
Jira Software = 9.12.x
Diagnosis
Run the following SQL to check for duplicate “Default context for Epic Status” entries in fieldconfigscheme. If more than one row exists, the instance is likely affected.
select * from “fieldconfigscheme" fcs where fcs."configname" = 'Default context for Epic Status';The duplicate rows in fieldconfigscheme gets cerated during Jira’s initial setup on PostgreSQL, specifically when a database OWNER is specified at database creation.
Sample query with which results in issue:
create database jira1 WITH ENCODING 'UNICODE' LC_COLLATE 'C' LC_CTYPE 'C' TEMPLATE template0 OWNER jira1Sample query which works fine:
create database jira1 WITH ENCODING 'UNICODE' LC_COLLATE 'C' LC_CTYPE 'C' TEMPLATE template0Cause
Jira fails to initialize the default options for the “Epic Status” field. This has been observed on PostgreSQL-backed Jira instances and reported on Jira 9.12.x. The issue has not been reproducible on Jira 10.3 and later.
Solution
When creating the database, please note that the user need not necessarily be the owner. However, it should have only the required privileges not more or less.
create database jiratest WITH ENCODING 'UNICODE' LC_COLLATE 'C' LC_CTYPE 'C' TEMPLATE template0 OWNER jira;
Create a Database in accordance with our article on Connecting Jira applications to PostgreSQL
Was this helpful?