- Integrations points
- Create issue from template
- Apply template
- Apply template post function
- Legacy automation action
- Template custom field on issue create screen
- Apply template via issue property
This chapter provides an information first steps in Issue Templates for Jira app.
As a new user you may wonder how to start working with Issue Templates for Jira app.
Following steps will give you a brief overview of the process.
Before you start, make sure you have all required permissions. Read the Permissions chapter for more information.
Set up Templates repository
Firstly, you need to choose a project, where your templates will be stored. Templates repository is a regular Jira project. All issues created in Repository automatically become templates.
For further information, navigate to Templates Repository chapter.
Configure UI visibility
(enabled by default, you can skip this step)
This option is enabled by default for all Jira groups. If you don’t need to make changes in UI Visibility, you can skip this step.
However, you can always disable Create from template buttons visibility. Thanks to that you can limit the number of users who can create templates.
Create a template
As a next step, create an issue in Templates Repository, so it will automatically become a template. Fill in issue fields.
There are no limitations according to template’s structure or complexity level. Issue Templates for Jira app copies Epics, Sub-tasks and Initiatives. You can even copy issue links and create new issues from linked templates.
Configure your template
(optional step; if you want to modify default settings)
Every template comes with a default configuration and is ready to use. However, you can adjust it to you needs in Template’s configuration. These settings can be edited at any time in Manage templates tab or on template’s issue view.
As you may know, issues have some defined, obligatory fields. These required fields with their values will be copied from template to target issue regardless any settings.
It means, that if a field is required in order to create an issue from your template, it will always be copied (without scope modification). It also means that you have to provide value for that field in your template.
If you want to copy fields that aren’t mandatory, you need explicitly add them to the Template’s fields or simply use handy All fields option in scope.
Optional fields, that are not included in scope, won’t be copied to an issue.
Create issue from template
(required steps, however you can decide how to create your template)
Before you start creating issues from template read more about:
There are three basic ways to create issue from the template:
Thanks to ITC solution, you can even create a link that directly opens the issue creation form with Template and other fields already selected.
Apply Template action is available in legacy automation in Jira Service Management projects.
It’s possible to use Jira Automation with external tool to apply templates to issue.
Issue Templates for Jira adds own JQL searchers to Jira, which you can use in every place where the JQL is supported.
Team-managed projects differ much from company-managed ones. Managing team-type projects is somehow problematic when it comes to using it with Jira applications. Read more about using templates in team-managed projects here.
Jira Software & Jira Service Management
Issue Templates for Jira app supports Jira Software Sprint field. You can add Sprint field to the scope. The Sprint ID will be copied, so that the template and new issue will share the sprint.
However, there are important hints that you need to keep in mind, before you start using it. For further information, read Jira Software chapter.
As all available apps, Issue Templates for Jira can’t interfere with the form displayed in the Customer Portal. It means that using templates in Jira Service Management may be limited.
Advanced roadmaps (Jira Software Premium)
Issue Templates for Jira app supports Advanced Roadmaps in Jira Software Premium. With ITC you can create an infinitive structures of Initiatives, Legends, etc. and copy whole structures from a template to issue.
Issue Templates for Jira can be integrated with the Issue Checklist app. You can use Checklist Content YAML and Checklist Text custom fields in your templates. However, there are some steps you need to make before you start. For more information, navigate to App integrations chapter.
Our app is constantly evolving. You can have an impact on ITC development, by Exploring & Voting. Simply navigate to the Roadmap chapter and see How can you contribute.