Child pages
  • Epic panel is empty and Epic is listed in the Backlog
Skip to end of metadata
Go to start of metadata

Symptoms

  1. Epic panel is empty
  2. Epic issue type is listed in the Backlog
  3. Creating new Epic via Create Epic link will not create an Epic issue type

Cause

The gh.epic.issue in SCRUM DEFAULT TEMPLATE is not pointing to the correct Epic issue type, hence there is not Epic listed in the Epic panel.

Workaround

Backup

The following changes are irreversible. Please ensure that the JIRA database backup is taken before proceeding to the resolution steps. It is also recommended that JIRA is taken out of service before starting the database backup.

After completing the resolution steps described below, please check the JIRA instance and the JIRA Agile configuration including user tests before bringing JIRA online. For e.g.

  • Do all the boards show up correctly
  • Are all the earlier sprints intact
  • Are the Story Points, Epic, Ranking and Business Value are correct in issues by doing a random check
  • Are the Sprint Reports and Burn-down charts intact (both Classic boards and Rapid boards)
  1. Run the following SQL query to obtain the SCRUM DEFAULT TEMPLATE

    select propertyvalue from propertytext where id = (select id from propertyentry where property_key ='SCRUM_DEFAULT_TEMPLATE_CONFIGURATION');
  2. From the results of XML output, you should see the following

    XML AttributeRelated Issue TypeSample XML
    gh.issue.epicEpic
    <entry>
      <string>gh.issue.epic</string>
      <string>6</string>
    </entry>

    From the above, we can see that the issue type ID that the Epic in SCRUM DEFAULT TEMPLATE is referring to is with ID=6

  3. Run the following SQL query to obtain the issue type ID for Epic issue type

    select id from issuetype where pname='Epic';



  4. If the ID from both SQL queries did not match, you would need to update the SCRUM DEFAULT TEMPLATE following the ID for Epic issue type (the second query). Example: When the result of the above query return '7'. Hence, updating the value for gh.issue.epic from 6 to 7.

    Sample Original XMLSample Updated XML
    '<map>
    <entry>
    <string>gh.issue.storypoints</string>
    <string>customfield_10004</string>
    </entry>
    <entry>
    <string>gh.issue.story</string>
    <string>6</string>
    </entry>
    <entry>
    <string>gh.issue.labelfield</string>
    <string>customfield_10003</string>
    </entry>
    <entry>
    <string>FIELDCONFIG_SCHEME_ID</string>
    <long>10102</long>
    </entry>
    <entry>
    <string>gh.issue.task</string>
    <string>8</string>
    </entry>
    <entry>
    <string>gh.issue.epic</string>
    <string>6</string>
    </entry>
    <entry>
    <string>gh.issue.businessvalues</string>
    <string>customfield_10005</string>
    </entry>
    <entry>
    <string>gh.issue.flaggingfield</string>
    <string>customfield_10002</string>
    </entry>
    </map>'
    '<map>
    <entry>
    <string>gh.issue.storypoints</string>
    <string>customfield_10004</string>
    </entry>
    <entry>
    <string>gh.issue.story</string>
    <string>6</string>
    </entry>
    <entry>
    <string>gh.issue.labelfield</string>
    <string>customfield_10003</string>
    </entry>
    <entry>
    <string>FIELDCONFIG_SCHEME_ID</string>
    <long>10102</long>
    </entry>
    <entry>
    <string>gh.issue.task</string>
    <string>8</string>
    </entry>
    <entry>
    <string>gh.issue.epic</string>
    <string>7</string>
    </entry>
    <entry>
    <string>gh.issue.businessvalues</string>
    <string>customfield_10005</string>
    </entry>
    <entry>
    <string>gh.issue.flaggingfield</string>
    <string>customfield_10002</string>
    </entry>
    </map>'



  5. Once the XML is prepared, update the database with the following:

    update propertytext set propertyvalue = <copy the contents from the text editor containing the XML here> where id = (select id from propertyentry where property_key ='SCRUM_DEFAULT_TEMPLATE_CONFIGURATION');
  6. Start JIRA.

  7. Reindex JIRA and test to see if you can use JIRA Agile without error.

(info) In case you are finding difficulties in any of the steps above, please contact Atlassian Support with a detailed description of the problem. It's likely we'll need to request your data so as to analyse the problem further and provide specific assistance.

Help us improve!
Unknown macro: {kbsurvey}
Unknown macro: {htmlcomment}

Regular Expression: ADD REGEX HERE (or delete the entire line)
ADD SUPPORT TICKET LINKS FOR REFERENCE