Designed with team productivity in mind, Issue Templates is an app that enables teams to save time and energy on repetitive issue creation.
Thanks to templates, teams benefit from ready-made issues that can be easily adjusted to different requirements. An issue template works like a model , showing users what to include or how a process looks like.
Templates not only boost team productivity but also reduce the risk of errors and ensure consistency when carrying out repetitive tasks.
Here’s an article I wrote about the benefits of templating.
We’re continually working on Issue Templates to deliver more value to our customers and help them build more efficient teams. Recently, we released version 7.0 of Issue Templates for Jira Server
Here’s an overview of issue tabs – the new feature included in Issue Templates app.
We revamped template configuration section in Issue Templates app by introducing a special issue panel. Thanks to these issue panel, users have the entire template configuration available in a single place, at the issue level.
Moreover, to create a new Scope users no longer have to waste time looking through the configuration of the project that serves as their template repository. Instead, the Scope can be set directly tab the panel.
Every main issue will now include the following tabs:
In sub-tasks, you’ll find two tabs: Scopes and Conditions.
Let’s take a closer look at each of these tabs to see the benefits they bring to team performance.
In this tab, users can name the template, set its category, and add a description.
Template name: Onboarding
Category: Human Resources
Description: This template includes sub-templates with tasks in the onboarding process.
The name of the template will be displayed in the drop-down list. Thanks to the template category, users can group templates and organize them on a list for ease of use. Seeing templates grouped by category helps to find the template you need quickly.
Both the description and category are displayed in the Templates summary section, allowing users to learn more about how to use the template instantly. For instance, the summary can include information about the template’s goal or the type of linked sub-tasks, helping teams choose the right template faster.
A scope is a set of fields and/or custom fields. The purpose of a given scope is defining which fields are used in a specific action, such as the Autocomplete feature or copying post-function.
For example, the Autocomplete feature automatically fills an issue with predefined values from a template. When you create an issue and use a template, selected field values will be automatically inserted into the new issue.
The copy values feature autofills predefined values from the template to a new issue. When a user creates a new issue using the template, these field values will be automatically inserted into the new issue based on a pre-configured workflow transition.
The section Scopes is divided into two parts: Autocomplete and Copy. In both cases, users need to name their set of fields and choose the fields to be included in this group to set the Scope. At least one functionality in the template needs to have a Scope.
All it takes is clicking the + sign to quickly create and save a new set of fields as a new Scope.
In this section, users can make the template active and available to everyone. They can also deactivate it – create a template with a complete configuration, but keep it inactive.
Moreover, users can choose the context in which a given template will be available. For example, you can configure a given template only to be available to users who belong to the group ‘Testers’ in the project called ‘TestFLO.’ If these conditions are met, users will have access to the template.
This tab is available to users who have installed Jira Service Desk. In this section, users can make a given template available on the Customer Portal.
For example, you can pick the request types and projects to which a given template will be available. If a template is active, but you choose no request types, it will automatically become available to all request types.
To help users search for templates, the request types in the drop-down list are preceded by the project name, for example, Trello.
This tab is available to users who have installed Jira Software. Before using that feature, the use has to first add Epic and Story to the project that serves as template repository.
It’s enough to add an issue of the type Epic and create an issue of the type Story inside it.
You can pick two options on this tab:
Note that the sub-tasks you create will include two tabs:
The InTENSO [Issue Templates] – Copy Subtasks post function must be configured as a stage in the post function configuration prior to adding stages to the template.
When no stage is selected on transition, only the sub-tasks with no stage (empty stage field) will be copied. You can decide when sub-tasks are to be created from the template during issue creation in a given project. For example, sub-tasks can be set to be created when they are linked to a given stage and meet a given JQL. These fields can also be left empty, or you can fill just one of them to match the needs of your team.
We hope that this change will improve the user experience with our app and help teams create and configure templates that make processes smoother and more efficient.
Have you got any questions about using issue templates? Get in touch with our consultants at email@example.com to learn how your team can become more productive.