Use cases

This chapter provides use cases - examples how Issue Templates for Jira can be used in practice.

How to benefit from multiple template repositories

Overview - multiple repositories

In this scenario you have several projects in your Jira instance. Most of these projects share similar workflows and can benefit from common templates.

There is one project that serves as a storage for templates for multiple software projects (global repository).

The Human Resources project wants to have its own templates, however, other projects don’t need to use these templates. This project can be converted into a local repository, so only members of this project are able to use templates stored here.

There are two projects at this point that store templates. One designated project for template storage that is set as a global repository, and one regular project that has some issues turned into templates that is set as a local repository.

With this kind of configuration you can avoid overfilling template selection and enable specific templates for specific projects.

Configuration - Multiple repositories

As explained before, such a configuration can be very useful in different scenarios. Here’s an example of such a configuration.

Enable both projects as repositories, one is set as global and one is set as local.

Global repository - template storage for multiple projects

1. Go to project configuration and set General settings accordingly. In this case every user of this project is able to turn issues into templates.

   

2. Manually or automatically enable issues as templates or simply add new templates to this project and set availability.

   

3. Check the list to see your active templates.

   

4. Use an existing scope or create a new one.

   

Local repository - template storage for a single/specific project

1. Go to project configuration and set General settings accordingly. In this case only a selected project role is able to create templates.

   

2. Manually or automatically enable issues as templates or simply add new templates to this project and set availability.

   

   Note

   To avoid creating templates uncontrollably, the automatic option is disabled by default. Contact your administrator if you want to have templates enabled automatically.

3. Create an issue and enable it as a template. You can set a scope and availability for each issue. This example uses dynamic variables.

   

   

4. Check the list to see your active templates.

   

5. Use an existing scope or create a new one.