Documentation for JIRA 4.2. Documentation for other versions of JIRA is available too.
On this page:
An Issue Type Scheme is a sub-set of issue types. An Issue Type Scheme allows you to:
An Issue Type Scheme can be shared across multiple projects, so that a group of similar projects can share the same issue type settings.
For example, in your company all projects may be one of two types, a development project or a support project. You could then create one scheme called Task with issue types Bug and Development and another called Support Issue Types, with Development Query and Support Request. You can then associate each scheme with the appropriate project(s), giving your users a different set of issue types depending on which project they decide to create issues in. Your future maintenance workload is minimised, because any change you make to a scheme is made across all projects that are associated with the scheme. In this example, adding a new issue type to all support projects only requires the simple step of adding the issue type to the Support Issue Types scheme.
The 'Default Issue Type Scheme' contains all the issue types that exist in your JIRA system. This scheme is associated with all newly created projects by default. If some of your issue types are not relevant to all of your projects, create one or more new Issue Type Schemes (e.g. 'Development Projects' in this screenshot) as described below, and associate them with the appropriate projects instead of using the Default Issue Type Scheme.
The process of editing a scheme is identical to the creation process. You can set defaults¹, reorder², add and remove issue types as before. However, if you're removing issue types from the scheme and there are issues associated with that issue type, you will be required to use the Issue Type Migration Wizard which will move your issues from the obsolete issue type to a valid one. Note that if you cancel out of this process at any time, your changes will not be committed. See below for more information about the migration wizard.
¹ ² Reordering issue types changes the order in which they are displayed to the user who is creating an issue; and the default issue type is the one that is displayed in the selection-box (see Creating an Issue).
You can restrict the issue types available by associating your Issue Type Scheme with various projects. Click the 'Associate' link and simply choose the projects that you wish your scheme to apply to. All selected projects will change from their current scheme to the selected scheme.
If the new scheme does not have an issue type that was present in the old scheme, you will be asked to use the Issue Type Migration Wizard to migrate the issues.
When updating a project you may often want to quickly restrict its issue types. However, the available Issue Type Schemes may not always be applicable, or you might not know which scheme to choose. The Select Issue Type Scheme screen makes this process simpler.
This Issue Type Migration Wizard allows you to migrate issues from an obsolete issue type to a valid issue type. The wizard will be triggered whenever an action (e.g. editing a project's issue type scheme) results in an issue type becoming obsolete (not available in the scheme).
The wizard bears some resemblance to the Bulk Move function except for that you can't change the project of the issues. The major steps are:
Steps 2 to 4 will be repeated for each issue type that requires migration. After you have migrated all the issues you'll see a summary of changes that will occur. If you click the 'Confirm' button, the wizard will migrate your issues to the new issue types and then complete your action.
Please refer to the Bulk Move documentation for more information on status changes and setting of fields values.