Beginner’s guide to Jira Administration – Part 2 (Issue Type Scheme)

Welcome to beginner’s guide to Jira administration part 2. In the part 1 of this series, we’ve discussed administration of Jira issue types. This articles continues where we left off.

Issue Type Scheme

Once relevant issue types are created, associate these issue types with relevant schemes. Issue type schemes are the mediators between projects & issue types (refer image below). This layer of abstraction helps in scaling the flexibility of the platform.

Some advantages of using a scheme as mediator (rather than direct assignment of issue types to projects) are

  • An issue type, once created, can be made available across different projects.
  •  Thus, projects of similar nature can rely on a single scheme. Just modify the scheme (if required), it would automatically apply to all associated projects.
  • Even if at some point two projects associated with a single scheme need to diverge in different directions, that becomes easier to manage. Just copy the scheme, update associations and then make changes to the relevant scheme/s.

Here’s how to navigate to issue type schemes. (again, you must be a Jira admin)


Issue type scheme – Actions


Button at the top right corner brings you to the add issue type scheme page. This page requires you to add name & description for the scheme. Just below that, the facility to manage issue types within the schemes is available. Via a drag drop interface, you can choose issue types applicable to this project. Right column lists all issue types available on your instance. Left column is where you’d drag the needed issue types.

You can also configure the default issue type. When creating a new issue (on projects associated with this scheme), what issue type is selected by default. Of course, you are free to set this to none. Meaning, issue creator is forced to select an issue type.


Editing an issue type scheme is exactly same as that of adding a new one. Just click on ‘Edit’ action from the issue type schemes listing page. This is how the page looks like.

Its important to note that if you are editing an existing scheme, existing issue types may need migration.  We’ll address this scenario in advanced administration articles.

Note – Order of issue types within the scheme, also determines their sequence in create issue screen.


Clicking on associate brings you to a page where one or more projects can be selected.

Copy, Delete

Copy & Delete actions are straight forward. Just make sure to be careful when you are deleting a scheme.

Default issue type scheme

All Jira instances have a default issue type scheme configured by default. This scheme cannot be deleted. This is a fall back scheme. If for whatever reason no scheme is associated with a project, this scheme will apply.

Common mistake

Typically, newbie Jira administrators tend to create new projects based on pre-defined templates.

This ends up in creation of different issue type schemes for every project. In a Jira instance with large number of projects, this can become messy.

Unless there is a strong reason for the new project to have its own configuration, its better to share config with other project/s. (Last option in the image below)

With this we conclude the Jira issue type related basic configuration stuff. Next, we will deep dive into issue workflows. If you have any questions, feel free to add them in the comments.

Anand is on a mission to help organisations build winning teams.
Share this article