Using templates
Three ways your team launches tickets from a template: from the issue menu, from a dashboard gadget, or prefilled into Jira's standard create-issue screen.
Three places templates launch from
Once a template is in your library, your team launches it from one of three places. Pick whichever fits your workflow.
From the Apps menu
This is the canonical path. Open any Jira page, pick Apps in the top navigation, then Create issue from template. A dialog lists every template you have permission to use. Pick one, fill the variables if any, and the ticket is created.
Detailed walkthrough: creating issues from templates.
From a dashboard gadget
Add the gadget to any Jira dashboard. Surface the three or four templates your team uses the most, and they launch in one click. Best for teams that create the same kind of ticket every day.
Detailed walkthrough: dashboard gadget.
Prefilled into Jira’s standard create-issue screen
When you want the user to confirm or override values before the ticket is created, pick Prefill new issues instead of the standard launch action. Jira’s native create-issue dialog opens with the template values pre-populated as defaults. The user adjusts and submits.
Detailed walkthrough: prefilling the issue creation screen.
Creating a whole hierarchy in one launch
For one-to-many cases, build a template that holds an Epic with its Stories and sub-tasks. A single launch then creates the entire tree at once, the parent and every child, with the links between them preserved. Useful for sprint setup, recurring work orders, and standing up the same structured set of issues every time.
Detailed walkthrough: creating issues from templates.
What happens to variables
If the chosen template defines variables, they are presented as a small form before the ticket is created. Text variables open a text input. Dropdown variables show a select. Date variables open a date picker. Reusable variables auto-fill from the value the user has already typed elsewhere on the form.
If a variable is marked as required and the user has not provided a value, the create action is blocked with a clear error message. If the template has no variables, the ticket is created instantly.
What happens to sub-tasks
When the template includes sub-tasks, the launch creates the parent ticket first, then each sub-task in order, with the same variable values propagated from the parent to every child. The result is a fully-linked ticket tree in a single launch.
Ready to template your Jira?
Install Process Templates for Jira on the Atlassian Marketplace. Free up to 10 users.