Get started
Templates helps you reuse the same work structure without rebuilding it by hand every time.
Create one template, run it whenever you need, and get prefilled work items in the right project and hierarchy.
Who can get started
You do not need to be a Jira admin.
If you can create work items in a project, you can usually:
create your own templates
use templates that others have shared with you
Project permissions still apply, but there is no special setup required before you try your first template.
If you need details, see https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2932506699 .
What you need before you start
You are ready if:
The app is installed on your Jira site.
You have at least one project where you can create work items
You have a process in mind that you repeat often, such as onboarding, release tasks and can use as a test case for app’s features.
That is all. There is no separate configuration step required before you begin.
Your first 10 minutes with Templates
Use these pages as a guided path.
Create your first template
Check out a guided configuration manual on how a template can be created.
→ See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2877947905.
Learn where to find templates while you work
See all the places in Jira where you can open and run templates as part of your normal workflow.
→ See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2778693635.
Explore the template library
Use the template library to review existing templates in your projects and discover what your team already relies on.
→ See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2141126684.
Check which fields are supported
Find out which fields Templates can prefill for you, so you know exactly what will be copied into each new work item.
→ See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2058682418.
Where to go next
Once you are comfortable with the basics, you can start using Templates to automate more complex work:
Apply templates to existing work items
Update an existing work item with a template instead of starting from scratch, so you can standardise work even if it already exists.
-> See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2877456386Keep templates flexible with variables
Use variables for names, dates or owners so one template can adapt to different projects, teams and scenarios.
-> See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2235236355Schedule work from templates
Use the scheduler to create work items from a template on a regular cadence, for example monthly maintenance or recurring reviews.
-> See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2888335397Run templates with automation
Trigger templates from Jira automation rules to create work items automatically when specific events happen.
-> See https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2448228356Build epic and subtask templates
Create epic templates with child work items or subtask templates to spin up whole structures in one go.
-> https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/2212233217Use easy cloning to copy and link related work
Create a new work item from a template and keep it linked to the original, so you can reuse proven patterns while preserving traceability.
-> https://stagil.atlassian.net/wiki/spaces/SCLJC/pages/850428091