Apps documentation
Issue Templates for Jira
Cloud Server/Data Center
Issue Templates for Jira

Cloud

Server/Data Center

Version 8.x
Version 7.x
FAQ
Release notes
Articles & Videos
Last updated Apr 16, 2023

Default Availability

Discover different ways to manage the availability of your templates

New templates are available and active by default. The Default availability settings allow you to define following configurations for all the templates in your Template Repository:

Tip

This feature is particularly useful for managing the availability of different issue types. While Template and Sub-Template issue types can be managed with the Disable Template post function in their dedicated workflow scheme, all other issue types can be defined here.

Note

All the following settings work only for newly created templates. The configuration won’t affect templates that already exist in your Template Repository project.

Configuration

Steps

To configure the default availability:

  1. Open the Template Repository project settings.
  2. Select Default availability from the project navigation.
  3. Click the arrow to expand all options.
  4. Decide if the templates should be available by default in all contexts.
  5. Configure the default context for new templates.
  6. Determine if defining context for existing and new templates should be required.
Jira Issue Templates - Default availability configuration
Issue Templates for Jira - Default availability configuration

Result

Configured settings apply to all the templates in your repository.

Tip

Scroll down to see possible configurations.

Make all new templates unavailable by default

Steps

To make templates unavailable by default:

  1. Open the Template Repository project settings.
  2. Select Default availability from the project navigation.
  3. Turn off the toggle next to Create Issue Screen.
  4. Turn off the toggle next to Request form.
Jira Issue Templates - Default availability: Make all new templates unavailable by default in all the contexts
Issue Templates for Jira - Default availability: Make all new templates unavailable by default in all the contexts

Result

All new templates will be unavailable by default.

Make all new templates available by default in all the contexts

Steps

To make new templates available by default:

  1. Go to Template Repository project settings > Default availability.
  2. Make sure that none of the contexts is set as required (or a default value is configured for each required field).
  3. Turn on the main toggle on the left side.
Jira Issue Templates - Default availability: Make all new templates available by default in all the contexts
Issue Templates for Jira - Default availability: Make all new templates available by default in all the contexts

Result

All new templates will be available by the default.

Note
  • Existing templates that already have a specified context will retain their settings.
  • The same applies to the Request form configuration.

Define a default context for new templates

Steps

To define a default context for new templates:

  1. Go to Template Repository project settings > Default availability.
  2. Under Default value for new templates, provide a value for the chosen context.
Jira Issue Templates - Default availability: Define a default context for new templates
Issue Templates for Jira - Default availability: Define a default context for new templates

Result

Availability of all new templates will be limited to the specified context.

Note

Existing templates will retain their settings.

Require that a context must always be defined

Steps

To require that a context must always be specified for every template:

  1. Go to Template Repository project settings > Default availability.

  2. Turn on the toggle next to the context that should be required.

    Note

    The global availability (the main toggle to the left) will be automatically turned off.

  3. Click Templates list in the info box to open a list of templates that have to be configured.

    Jira Issue Templates - Default availability: Require that a context must always be defined
    Issue Templates for Jira - Default availability: Require that a context must always be defined

    Info

    You will be redirected to the Template navigator where you’ll see a filtered out list of all the templates that require additional configuration.

  4. Select the template that needs to be configured and open its Availability tab.

  5. In the info box, click Configure now.

    Jira Issue Templates - Default availability: Require that a context must always be defined
    Issue Templates for Jira - Default availability: Require that a context must always be defined

    Warning

    After clicking Configure now the template will become unavailable for the time of the configuration. You’ll be able to make it available again after filling in all required fields.

  6. Click the arrow to expand all options.

  7. Define a value for the required context.

  8. Turn on the toggle to make the template selectable on the Create issue screen in the specified context.

    Jira Issue Templates - Default availability: Require that a context must always be defined
    Issue Templates for Jira - Default availability: Require that a context must always be defined

Result

The chosen context is set as required. The template is configured to be selectable in the specified context.

Note

The same applies to the Request form configuration.

Need help?

If you can’t find the answer you need in our documentation, raise a support request.