Restricting Templates usage

The Template usage depends on two fields in the Template configurations:

1. The ‘Available for’ field

2. The 'Scope' field

The ‘Available for’ field response on who can apply the Template. It has got two options:

• Owner

• Scope
  You can choose the ‘Owner’ option, in the ‘Available for’ field, this is allowed to use the Template, only for the owner of the Template not for the scope.

You can choose the ‘Scope’ option in the ‘Available for’ field if you want to share the Template with other users. This allows to use the Template for each user that has access to projects that were listed in Scope and has one of the groups defined in the Scope.

The Scopes field restricts where and whiсh groups of users can use the Template.

For example:
'My Template' template with ‘My Scope’ scope:

It is applicable for:

• The Issue in the Scrum Software project

• The Issue of any issue type

• For any user in any group.

Restrict Template to certain Issue Type(s) across all Projects

You can restrict the Template scope by certain issue type(s).

For example:
'My Template' template with the ‘My Scope’ scope

It is applicable for:

• The Issue in any project

• Issue Type was set as Task or Story

• For any user in any group.

Restrict Template to certain Issue Type(s) in certain Project(s)

You can restrict the Template scope by certain issue type(s) in certain Project(s).

For example:
'My Template' template with the ‘My Scope’ scope

It is applicable for:

• The Issue in the Scrum Software project

• Issue Type was set as Task or Sub-task

• For any user in any group.

It will not be available for any other Issue Type under Scrum Software (SSD) Project or Task and Sub-task Issue Type under a different project.

Restrict Template to certain Groups

You can restrict the Template to a certain group of users.

Similar to restrictions by Projects and Issue type you can set restrictions by a certain user’s group. Only users that were joined to one of the listed groups can use the Templates with Scope on the screenshot.

For example:
'My Template' template with the ‘My Scope’ scope

It will applicable for:

• The Issue in any project

• The Issue can have any issue type

• The user that performs action is the
  developers-team group member.

Restrict Template to certain Users

You can restrict the Template to certain users.

For example:
'My Template' template with the ‘My Scope’ scope

It will applicable for:

• The Issue in any project

• The Issue can have any issue type

• The user is the SoftwareUser

The restrictions by Group also work in pairs with Projects and Issue Types.

For example:
'My Template' template with the ‘My Scope’ scope

It will applicable for:

• The Issue in the Scrum Software project

• Issue Type was set as Story or Bug

• The user is the SoftwareUser (who is a member of the developers-team group)

No Restriction (Global)

If you want to create a Template that is available anywhere in Jira you can use a special scope named GLOBAL. Also, you can create your own global Scope for your Templates, just leave all of the Scope fields (except the required field Name) empty for it.

For example:
'My Template' template with the ‘My Scope’ scope

It can be used in the Issue with any configuration.