JIRA Documentation

JIRA 6.3 EAP
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

Issue Types are missing from the Default Issue Type Scheme. This may cause loss of functionality for issue related functions (i.e. moving or creating issues).

Cause

The root cause is due to manually editing the optionconfiguration table in JIRA database.

Resolution

Icon

Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.

Currently the workaround involves direct editing of JIRA's database. The related tables are titled issuetype and optionconfiguration.

Insert a new row into the optionconfiguration table, with the appropriate issue type (optionid) and scheme (fieldconfig):

  1. Ensure that the optionid column from the optionconfiguration table is the same as id column from the issuetype table.
  2. Ensure that the Default Issue Type Scheme is represented by the value '10000' in the "fieldconfig" column of the optionconfiguration table.
  3. Restart JIRA after editing.
Icon

For example, running the following code will pull up all the necessary information for the issue type 'Bug'

id

sequence

pname

pstyle

description

iconurl

id

fieldid

optionid

fieldconfig

sequence

1

1

Bug

 

A problem which impairs or prevents the functions of the product.

/images/icons/bug.gif

10030

issuetype

1

10001

1

1

1

Bug

 

A problem which impairs or prevents the functions of the product.

/images/icons/bug.gif

10034

issuetype

1

10000

0

(info) When inserting a new row into the optionconfiguration table, a unique id must be given.

Related Content

Help us improve!
Is this article helpful?
Is the content complete?
Is it well written?

4 Comments

  1. looks like a similar error may occur if the fieldconfigschemeissuetype table is missing the default scheme

  2. The related issue is  JRA-22987 - Issue Types Missing from the Default Issue Type Sheme Resolved  

    I was able to move issues using Bulk Change instead of Move.

  3. Another way this happens is when creating new Issue Types during a CSV import. These issue types do not get added to the Default Issue Type Scheme.