Default Issue Type Scheme does not list the Bug Issue Type

Issue Summary

The default Issue Type Scheme does not list the Bug Issue Type.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Created two new Jira instances (8.20.11 & 9.4.6).
2. Checked that the Bug Issue Type is not listed under the Default Issue Type Scheme.
3. Added a new Issue type 'Test' which did show up under the Default Issue Type Scheme.
4. But not the Bug Issue Type. Screenshot for reference :
   • 

Expected Results

Bug Issue Type should show up in the list.

Actual Results

Bug Issue type does not show up in the list

Workaround

• The solution mentioned in the Article: Issue type invalid error thrown when moving an issue to another type in Jira server helps resolve the problem.

• As most default schemes in JIRA the "Default Issue Type Scheme" is read-only, so we need to manually add the missing issue types through the database.
  If you are using JIRA Cloud please reference this document for the workaround.
  As manual data manipulation will be necessary, please make sure you have an up-to-date backup of JIRA.
  The SQL shown below applies to PostgreSQL and may need to be modified to work in other databases

   

  • Shut down JIRA;
  • Identify the missing values:

    SELECT id, pname FROM issuetype WHERE id NOT IN (SELECT optionid FROM optionconfiguration WHERE fieldconfig = 10000 AND fieldid = 'issuetype');

  • Use the following SQL statement to add the missing entries from previous step. Repeat the query as many times as necessary until you've added all missing issue types;

    INSERT INTO optionconfiguration VALUES ((SELECT MAX(oc.id)+1 FROM optionconfiguration oc), 'issuetype', '<missing_issue_type_id>', 10000, (SELECT MAX(oc.sequence)+1 FROM optionconfiguration oc WHERE oc.fieldconfig=10000));
     Replace {{<missing_issue_type_id>}} with the ID of the missing field;

  • Fix the sequence_value_item table to avoid key violations

  • • UPDATE sequence_value_item SET seq_id = (SELECT MAX(id)+100 FROM optionconfiguration) WHERE seq_name = 'OptionConfiguration';

  • Start JIRA
  • Go to Administration > System > Indexing and perform a full re-index by selecting the Lock JIRA and re-build indexes option;

• We have tested and it worked.

Note :

This requires data manipulation so there's always a concern.