This chapter provides use cases - examples how Issue Templates for Jira can be used in practice.
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.
As you can see, there is one template for this project here and some regular issues.
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.
See the section below for more detailed configuration.
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.
Go to project configuration and set General settings accordingly.
In this case only a selected project role is able to create templates.
Manually or automatically enable issues as templates or simply add new templates to this project and set availability.
To avoid creating templates uncontrollably, the automatic option is disabled by default. Contact your administrator if you want to have templates enabled automatically.
Create an issue and enable it as a template. You can set a scope and availability for each issue. This example uses dynamic variables.
Check the list to see your active templates.
Use an existing scope or create a new one.
Issue Templates for Jira Cloud offers a feature that will automatically create respective version and component according to the template. For example, a project that stores software templates contains specific versions and components. If you use this template in other projects that don’t have these items, they will be automatically created.
Your issue has been created based on the template and versions/components were added to this Jira project.
Read more:
In this scenario, a user wants to have a template that would automate the process of implementing a new feature. With smart defaults, the process can automate:
In this case, smart defaults are configured as follows:
See Atlassian support for details on checking the ID of a custom field.
The feature name will be automatically applied to the referred fields, such as the summary, new feature idea in the description and the label in this case.
Once the template is configured, the user can navigate to the create from template option to use it.
You will be asked to fill in the feature name, description (user story), and the version.
The output looks like this:
In this scenario, a user wants to plan an event and add steps in form of a timeline. With smart defaults you can offset dates easily, as well as copy values from parent and linked issues. An epic is created that corresponds with planning steps. Steps are added as stories and an epic for a corresponding process that happens simultaneously is linked.
Child issues are configured using smart defaults to shift one week forward and copy components and the assignee from the parent.
The linked epic is also configured to copy the due date from the main task and shift it in time.
Both epics have been created and child issues with set values have been applied.
Child issues copied the assignee, components, and shifted the date as configured.
Due date of the linked epic has also been shifted.
You can configure an epic link or a parent in smart defaults so that it will link to an already-existing epic. This way templates will automatically link to the specified epic in this project or another.
See How to use smart defaults for details.
You can prepare a template for onboarding purposes that includes a checklist. In this scenario, a checklist corresponds with necessary access levels for a new employee.
