Screen schemes group screens together and create associations with issue operations. The next piece of the puzzle is to tell JIRA to use our screen schemes when creating, viewing, and editing specific types of issues.
We do not directly associate screen schemes to JIRA. The reason for this is that JIRA has the flexibility to allow you to define this on a per-issue type level. What this means is, instead of forcing all the issue types in a given project to use the same screen scheme, you can actually use different screen schemes for different issue types. This extremely flexible and powerful feature is provided through the issue type screen scheme.
Just like screens and screen schemes, you need to be a JIRA administrator to create and manage issue type screen schemes. Perform the following steps to manage issue type screen schemes:
Just like screen scheme, JIRA will automatically create an issue type screen scheme when you create your project. Since one project can only have one issue type screen scheme associated, usually you will not need to create new ones yourself. However, there might be a time when you want to create a new scheme, such as experimenting with some new configurations while still wanting to keep the existing one untouched in case of a roll back.
Perform the following steps to create a new issue type screen scheme:
That's right, you guessed it! The new issue type screen scheme is not yet in use. It will only become active once it is applied to one or more projects, which we will look at shortly.
You can make updates to an existing issue type screen scheme's name and descriptions. To change its screen scheme/issue type association details, you need to configure the issue type screen scheme, which will be covered in later sections. Perform the following steps to update an issue type screen scheme:
Just like all other schemes in JIRA, you cannot delete issue type screen schemes that are in use. You will have to make sure that no project uses it before JIRA allows you to delete the scheme. To delete issue type screen schemes perform the following steps:
Issue type screen scheme cloning is also available in JIRA. You can easily make copies of the existing issue type screen schemes. One very useful application of this feature is that it enables you to make backup copies before experimenting with new configurations. Note that copying the issue type screen scheme does not back up the screen schemes and screens that it contains.
Perform the following steps to copy an existing issue type screen scheme:
The newly created issue type screen schemes are inactive by default, while cloned schemes are not used by any projects.
By creating new issue type screen schemes, you can establish new associations between screen schemes and issue types. These associations are what tie the projects and issue types to the individual screens.
Each issue type screen scheme needs to be configured separately, and the associations created are specific to the configured scheme:
JIRA determines which screen scheme to use for an issue type by establishing an association between screen schemes and issue types. Each issue type can have only one screen scheme associated with it. However, each screen scheme can be associated with more than one issue type.
Perform the following steps to add a new association:
As shown in the preceding screenshot, the Story,Task, and Bug issue types are explicitly associated with DEMO: Scrum Story Screen Scheme
, Demo: Scrum Task Screen Scheme
, and DEMO: Scrum Bug Screen Scheme
, respectively. All other issues types, such as Improvement, will be associated with the default DEMO: Scrum Default Screen Scheme
.
You can update the existing associations, such as the Default association, which is created automatically when you create a new issue type screen scheme:
You can also delete the existing associations for issue types if you no longer need them to be explicitly set. However, you cannot delete the Default association, since it is used as a catch for all the issue types that do not have an association defined. This is important because while you may have created associations for all the issue types right now, you might add new issue types down the track and forget to create associations for them. To delete an association:
Just like associations in screen schemes, you will not be taken to a confirmation dialog, and the association will be deleted immediately.