Issue Templates in Jira: Guide 2025

[#1]

Creating the same repeatable workflows over and over again? That’s a task for a template, not a human! In this guide, we’ll walk you through everything you need to know about issue templates in Jira. You’ll see what native options exist, how to work around Jira’s limitations, and when it makes sense to use external tools. 

We’ll also share real examples, reusable templates, and best practices. In addition, you’ll find here hands-on tips and answers to the most common questions. All this will help you build templates that actually work for your team 🏆

What Native Templates Are Available In Jira?

Project templates

These templates help you create new projects with everything set up in advance. Each one includes pre-set work types, workflows, a Jira board, custom fields, and built-in reports. Project templates are tailored for specific use cases and industries, so you can pick the one that matches your needs. An example of this type is the Kanban project template, Scrum, Project Management, and DevOps project templates. In addition, Atlassian now allows customers to create their own project templates.

Request type templates (Jira Service Management)

Request types define how teams handle service requests. Each type comes with its own form, workflow, and SLA rules. These templates help internal teams like IT, HR, or Finance collect the right details and follow a consistent process. The examples of such templates are “Request new software” or “Onboard a new employee” requests.

Work item layouts

In team-managed projects, you can define how each work type is displayed. This includes choosing which fields are visible, what order they appear in, and how they’re grouped into sections. For example, you can show Severity and Affected Version right below the work item summary in Bug reports, while hiding them in Tasks. These layouts help different teams focus on the fields that matter most to them. However, it’s important to note that these layouts are not work item templates (issue templates). They don’t allow you to reuse a task structure, such as description, assignees, included checklists, and so on. 

The templates we’ve covered so far focus on a higher level of workflow management: setting up projects, request types, and work item layouts. They are useful for defining the overall structure of your Jira environment. But once the project is in place, teams still need to create and manage individual work items - tasks, bugs, stories, and so on. These often follow recurring patterns. That’s where work item templates come in. They help teams avoid repetitive setup work, reduce the risk of missing steps, and keep daily task management consistent.

Does Jira Offer Work Item Templates Out of the Box?

No, Jira does not provide native work item templates or reusable task structures with subtasks. So, basically, you have two options:

• Use a workaround - such as cloning work items to reuse their structure or set up automation to create work items based on triggers. These workarounds allow you to partially solve the problem and can be a good fit for organizing some workflows. However, their capabilities are limited as these features are not dedicated for creating Jira work item templates.
• Find a dedicated solution - on the Atlassian Marketplace, you can find a solution that fits this purpose better, such as Smart Templates for Jira. This app allows you to create reusable templates for any issue type, including epics with sub-issues. Such templates can include pre-filled fields and descriptions, variables, checklists, and more. It’s a practical way to document recurring tasks and processes and avoid starting from scratch each time.

Let’s explore each of these options in more detail.

Workaround 1: Cloning as a Substitute for Work Item Templates in Jira

Cloning is Jira’s built-in option for quickly copying a task. You can use it to duplicate a previously created task and make edits for the next iteration. While it’s not a full replacement for real templates, it can work in simple cases. For example, when you need to reuse the work item description, overall structure, fields, or checklist. This can be a good option when you only need to reuse all this information rarely - let’s say, for a yearly report.

When you clone a Jira work item, Jira creates a new task with pre-filled content from the original. By default, the following fields are copied:

• Summary (with the word “CLONE” added at the beginning)
• Description field
• Checklists 
• Attachments
• Assignee and Reporter
• Priority and Labels

To clone a work item, open the original task, click the three-dot menu in the top right corner, and select Clone. Jira will create a new work item in the same project. You can edit the details right away and update the fields as needed. 

For more complex cloning scenarios, please have a look at our Cloning in Jira Guide 2025.

Pros of Using Cloning 

• Built-in feature
• No additional setup required
• No special permissions needed
• Quick to access and use
• Good for rare or one-off tasks
• Copies a large amount of information at once
• Works well for simple, flat structures

Cons of Using Cloning as a Substitute for Jira Work Item Templates

No full hierarchy support

Cloning can preserve child work items, but only one level deep. If you clone an epic, Jira will copy the epic and its direct child work items (like stories or tasks), but not their subtasks.

Manual cleanup required

Cloned work items carry over all the original details, including names, descriptions, and field values. You’ll have to review and edit each one to remove outdated or irrelevant content that is not needed for a new task.

Risk of editing the source 

If someone accidentally edits the work item used for cloning, all future copies may carry incorrect or irrelevant information.

Scattered and hard to track

There’s no central place to manage or find cloned templates. Teams may lose track of which work item was meant to be reused.

Not scalable

Cloning might work for a single task, but doing it repeatedly across teams or projects quickly becomes time-consuming and error-prone.

Not designed for template management

Cloning was never intended to be used instead of work item templates, so key features are missing. You can’t use dynamic values, schedule recurring tasks, or track how and when work items were cloned. You also need to manually configure and double-check the cloned work item each time to avoid errors.

Workaround 2: Creating Identical Work Items with Automation for Jira 

Jira has built-in Automation functionality that can be used as another workaround. It allows you to generate multiple work items with the same structure based on an automation rule. This method is better scalable than cloning. While it doesn’t offer true Jira work item templates, it can mimic their behavior if configured well.

Automation allows you to specify: 

• Trigger  - the event that starts the rule, such as work item creation (issue creation).
• Set of conditions - filters that define whether the rule should run. For example, “work item name contains Onboarding”.
• Action - what happens if the conditions are met. For example, adding a standard description and fields for the onboarding tasks.

How to Set Up Automation to Create Identical Work Items

Go to Project Settings > Automation and click Create Rule. Choose a trigger (like a manual trigger or status change), set any conditions you need, and add the Create issue action. There, you can pre-fill various fields including Summary, Description, Priority, Epic link, Assignees, linked issues, and more. Once everything is set, save and publish the rule.

Here’s an automation rule for the example we mentioned earlier. Once a new work item is created, if its summary (task name) contains “Onboarding”, a templatized description for the onboarding tasks will be added. Also, the new work item will be automatically assigned to the person responsible for onboardings. In addition, it will have the specified priority level - in this case, Highest.

In the Atlassian community, you can find other rule examples used as a workaround. But they need to be tested thoroughly before applying, as not all of them are stable and may not always work as expected.

Pros of Using Automation 

• Built-in functionality
• Supports scheduled and event-based triggers
• Can create multiple work items at once
• Works across different projects
• Allows use of conditions and branching logic
• Preserves field values and relationships
• Better suited for recurring structured tasks than cloning

Cons of Using Automation as a Substitute for Jira Work Item Templates

Requires admin access

In most cases, you need project admin or global admin permissions to create or manage automation rules. This limits who on the team can set them up, make updates, or share.

Admin-only error handling

Automation for Jira doesn’t always run smoothly. If a rule fails, only admins can resolve the problem, which adds extra steps and delays. In case of multiple or frequent errors, the process becomes inefficient.

Learning curve for setup

Creating automation rules often requires technical understanding and familiarity with Jira’s logic. Non-technical users may need training or support to use automation effectively, especially when working with branching, smart values, or dynamic field mapping.

No true template library

There’s no place to browse, manage, or reuse predefined work item structures. All configurations live inside automation rules, so there’s no transparency.

No full hierarchy support

Jira Automation can create a parent work item along with its direct child work items. For example, an epic with stories or a task with subtasks. However, it doesn’t support deeper levels, so you can’t automatically create subtasks inside those child work items.

How to Create Real Work Item Templates in Jira With Smart Templates

As you can see, the workarounds are not the best way to build Jira work item templates. These alternatives can get cumbersome and inefficient, and, at the same time, don’t give you exactly what you need. For a simpler way to create structured work items, Smart Templates are a better fit. 

There’s no need to set up complex automation rules or keep track of the “model” work items to clone. Smart Templates is a dedicated tool made specifically for creating and managing work item templates in Jira, so it’s equipped with all the necessary functionality.

Here are some key features of this app:

Template library

You can create, view and manage all your templates from one place, where they are organized as a list. That’s where you can create new issues (work items) from a template in just a few clicks. This is also a great option for knowledge sharing as you can easily share information on how a specific process should be run.

Template variables

The app supports variables - elements that allow you to set dynamic values for fields that change from one task to another. For example, for onboarding tasks, new hires’ {{name}} and {{position}} can be variables. This allows you to easily adjust work item content for a specific task.

Full work item hierarchy

Smart Templates can fully preserve a complex work item hierarchy - for example, an epic with tasks, subtasks, and checklists. Such an epic can be saved as a reusable template like any other work item.

Template scheduler

You can schedule automated work item creation according to your preferences. This can be done with Smart Templates’ built-in functionality, so you don’t have to set up any rules in Automation for Jira. This is useful for recurring tasks, such as monthly reports.

Template history

Each template has a history log, so you can see the list of all work items created from this template and their status. This helps you keep track of your work item templates in Jira and see where they are used.

Pre-filled fields

Templates can include default values for fields like assignee, priority, or components to keep work item setup consistent. This can be both standard and custom fields. 

Integration with Automation for Jira

In addition to scheduling, you can also use Smart Templates with Jira Automation for more advanced scenarios. This is useful when work item creation depends on specific triggers, such as a status change or a custom field update. With this setup, you can apply a template automatically based on your team’s workflows. It’s a flexible way to connect templates with your existing processes and reduce manual steps in recurring work.

Types of Work Item Templates in Jira You Can Build With Smart Templates

There are two main types of work item templates you can create with the help of this app:

• Work item description template - Preserves a Jira work item structure with its summary, description, pre-filled fields, checklists, and more. You can save any work item as a template and reuse it multiple times. Variables make it easy to adapt template content to a specific task.
• Task hierarchy template - Captures a full structure of a parent work item with all its child work items. This can be an epic with multiple child tasks and subtasks. Each work item in the hierarchy can have its own content, pre-filled fields, descriptions, checklists, and so on. This is useful for recurring multi-step processes - for example, hiring or compliance review. Smart Templates allow you to easily create a work item with all its dependencies from such a template.

Using Smart Templates allows you to significantly optimize processes. It saves time, promotes standardization and consistency, and allows you to organize work more efficiently.

How to Create a Work Item Description Template

Here’s an example of a task description template. Let's say a software development team needs to frequently run multiple tests. To optimize this process, they can use this template. It documents a structure for writing case-specific tests so that you only need to fill out the required details.

To create a similar Jira work item description (or issue description) template, follow these steps:

1. Install Smart Templates for Jira from the Atlassian Marketplace.
2. Open the work item that you want to turn into a template - an epic, task, etc. Alternatively, create one from scratch. 
3. Make all the edits that you want to be included in your template. Pre-select assignees, fill out work item fields, add variables, and so on. 
4. Save the structure as a template from the Smart Templates section of your Jira work item (Jira issue).

Let’s see an example showing how to use variables in Jira work item templates. Go to the Variables tab in the Smart Templates menu. Provide variable names and types - these can be dates, drop-down lists, people (Jira users), and so on.

When creating a new work item, you will be prompted to provide/select values for the variables. In the example below, we had Test Case: {{Feature_name}} || {{Product}}. When we created a new work item from this template, variables were substituted with the actual feature name and product name. 

This allows you to easily adjust description templates to specific tasks.

That’s it! Your template is ready. Optionally, you can also add checklists to your work item templates in Jira. This can be done with Smart Checklist for Jira, which is another useful tool offered by Titan Apps. It’s well integrated with Smart Templates, so both apps work together seamlessly. As a result, you will get a more detailed and useful template.

3 Ready-To-Use Jira Work Item Description Templates

Here are some examples of work item description templates for software development teams. They can be used with Smart Templates. Just copy the description into a Jira ticket, adjust it to your needs, and save the work item as a template.

1. Bug Report Work Item Template for Jira

Environment

// Please fill out the following:

Operating system: {e.g. MacOS, Windows10}

Browser and version: {e.g. Chrome 124.0, Safari 17.4.1}

Software version: {e.g. V1.51}

Environment: {e.g. prod, staging, testing}

Steps to reproduce

// Please add the steps that are necessary to reproduce a bug

1.

2.

…

Actual Result

// Please explain what happens when the bug is reproduced

…

Expected Result

// Please describe how the functionality is intended to work

2. User Story Work Item Template for Jira

User Story

As a {type of user}

I want to {goal to achieve}

So that {value or benefit this brings}

Context

// Brief explanation of the feature or user need

…

Acceptance Criteria

// List the conditions that must be met for this story to be considered complete

1.

2.

3.

…

User Flow / Steps

// Optional: Describe the typical steps the user would take

1.

2.

3.

…

3. Generalized Test Case Work Item Template for Jira

## Test Case {{Number}}: {{Feature_Name}} || {{Project}}

Description:

[Briefly describe what this test case verifies]

Priority: {{Priority_level}}

Type: {{Type}}

Preconditions:

[Any setup required before execution]

[Example: User is logged in]

Test Steps & Expected Results:

Step 1: [Describe action]

Expected result: [Describe expected outcome]

Step status: [Not run/Passed/Failed/Blocked]

Step 2: [Describe action]

Expected result: [Describe expected outcome]

Step status: [Not run/Passed/Failed/Blocked]

Step 3: [Describe action]

Expected result: [Describe expected outcome]

Step status: [Not run/Passed/Failed/Blocked]

Test Status: Not run

Additional Notes:

[Include any additional observations, logs, or screenshots]

How to Create a Task Hierarchy Template in Jira (an Epic With Subtasks Template)

To capture complex processes, it’s useful to create a templatized set of tasks gathered under one epic. This is especially helpful for processes with multiple stages stretched in time, several assignees, and numerous steps.

The screenshot below shows how we manage a recruitment flow with the help of an epic documenting this process. The original epic, which includes tasks, subtasks, and checklists, was saved as a reusable structure. Each time we start hiring for a new role, we generate a new epic from that template to keep the process consistent. 

A similar approach can be applied to other complex processes: compliance preparation, launching a marketing campaign, and so on.

With Smart Templates, you can easily save a complex work item hierarchy as a reusable template. To do so, you need to complete the same steps as for creating a template out of any other work item:

1. Install Smart Templates for Jira.
2. Open the Jira work item you want to turn into a template. This can be a parent work item with several levels of child work items and checklists. The details of each work item in the hierarchy (descriptions, fields, etc.) will be preserved in the template. 
3. Save the task hierarchy as a template from the Smart Templates section of your Jira work item.

If necessary, add variables for the changing elements - a project name, collaborator’s name, etc. We described how to add variables to smart templates earlier in this article. Please refer to the previous section for details. 

Additionally, include checklists with the help of Smart Checklist for Jira. This will make your templates even more valuable for your team.

Examples of Work Item Templates in Jira For a Parent Task With Child Tasks

Example 1: Marketplace Release Template

Each time you release a new app update, you need to complete the same steps to submit it to the App Store. So, instead of planning this activity from scratch over and over again, you can generate a ready-to-use epic from a template in just a few seconds.

The screenshot below shows such a structured marketplace release template, which is built as an epic with a set of tasks and checklists. 

Example 2: Passing Security Certification Template

Imagine you manage several products across different Jira projects, and you need to get them ready for a security compliance audit. This means you have to complete the same sequence of tasks for each product. To handle this, you can create a template in the form of an epic that includes all the necessary tasks.

Example 3: Test Case Template For Recurring Testing

If your team releases software updates bi-weekly, you will need to repeatedly test the same features every time. Using a test case template can simplify this process. You can organize the test suite as an epic with multiple work items. Each of them can represent a specific test task with defined steps. 

Using Automation With Work Item Templates in Jira

There are several automation options available with Smart Templates. The first one is a built-in functionality for generating new Jira work items on a schedule. Another option is integrating Smart Templates with any solutions you have with the help of webhooks. And, finally, for complex rule-based scenarios, Smart Templates can be integrated with Automation for Jira. Let’s explore this in more detail.

How to Generate Work Items From Templates Automatically on a Schedule

Smart Templates includes a built-in Scheduler that lets you automatically create work items from a template at set intervals. This works for both work item description templates and task hierarchy templates. It’s useful for any recurring process, like bi-weekly testing, regular audits, or scheduled reviews. 

In the example below, the Scheduler is set to generate a test suite epic with sub-tasks every other Wednesday. This ensures that, when it’s time for regression testing, QAs will have their tasks ready and pre-assigned.

To set it up, go to your list of Smart Templates, select the one you want, click the three-dot menu, then choose Edit → Scheduler.

How to Integrate Jira Work Item Templates In Custom Automation Scenarios

You can use Smart Templates in various custom automation cases. This includes rule-based automations, cross-tool integrations, and advanced setups for recurring processes.

Webhook links

With the help of webhooks, you can trigger work creation from a template through Jira Automation or third-party tools like Postman. To get the webhook link, open the template, go to the Automation tab, and click Generate webhook. Then copy the link and paste it into the automation rule or tool you’re using. This method works well for scheduled triggers, external tools, or custom workflows that go beyond Jira’s default options. 

Integration with Automation for Jira

Smart Templates also integrate directly with Automation for Jira. For example, you can apply a specific template to every work of a certain type. If your team creates test cases regularly, add a new work type called Test Case. Then, set up a rule that inserts the test case template into each new work of this type. This is just one of many examples of how Smart Templates can be used with Automation for Jira. For more details, please see the Smart Templates Documentation.

Integration with Jira Service Management

You can also combine templates with Jira Service Management requests. When someone submits a request of a specific type, the matching template can be applied automatically. This is useful for approvals, onboarding, or any other request that follows a fixed structure.

These integrations help you embed templates into your Jira workflows and reduce repetitive manual work.

Common Reasons for Implementing Jira Work Item Templates

Implementing work item templates in Jira often starts with a need for more structure and efficiency. As teams grow or processes become more complex, creating repetitive tasks manually leads to delays and inconsistencies. Templates solve this by standardizing how tasks are generated. They make it easier to apply the same structure across different projects and teams. This not only saves time but also helps reduce human error. 

With templates, all required steps and fields are included from the start. So, instead of relying on memory or scattered examples, teams can use templates and follow clearly documented processes. Templates improve cross-team alignment by providing a shared structure that everyone can work with. In fast-paced environments where teams need to launch projects quickly or delegate tasks effectively, having reliable templates in place can make a noticeable difference. This helps teams increase their work speed, quality, and consistency.

Best Practices for Using Jira Work Item Templates

Keep templates focused and specific

Avoid making templates too broad. Each template should cover a specific use case to prevent confusion and reduce unnecessary edits.

Name templates clearly

Use naming conventions that describe the purpose of each template. The name should be easy to understand for everyone. For example, “Definition of Done Template” or “Onboarding Process Template.” This makes them easier to find and apply.

Use variables for dynamic data

Instead of rewriting content each time, use variables for fields like names, dates, or team members. This makes templates easier to reuse with minimal changes.

Maintain templates as living documents

Templates should reflect your current process. If the way your team works changes, update the templates so that they stay relevant. Review them regularly to streamline your processes, identify gaps for optimisation, and align the documented workflows with the real workflows you have.

Use a dedicated app that matches your needs

Issue templates Jira are not offered natively, and the available workarounds can only partially help. Select a marketplace app that provides the functionality your team needs. This can be Smart Templates - a dedicated app that supports templates with full hierarchy, scheduling, variables, and automation.

Include checklists when applicable

For repeatable tasks that involve multiple steps, add checklists to guide the process. This helps teams follow the correct steps without needing extra guidance. You can use Smart Checklists for Jira to add checklists to your Jira issue templates.

The Benefits of Using Work Item Templates in Jira

When you organize your work with templates effectively, this allows you to speed up processes, reduce errors, and improve communication. In particular, you can:

• Save time on creating recurring tasks
• Maintain consistency across projects and teams
• Reduce the risk of missing steps or required fields
• Make processes easier to follow, especially for new team members
• Improve cross-team coordination with a shared task structure
• Avoid manual setup of multi-step work hierarchies
• Streamline processes and make them more fast-paced
• Keep task structures aligned with internal standards

As a result, you have a better-organized team that completes work faster.

FAQ for Work Item Templates in Jira

What Are Work Item Templates Jira?

Issue templates in Jira are reusable work item descriptions, full work item structures, and templatized work item hierarchies consisting of multiple work items. Sometimes they are also referred to as Jira ticket templates. They help teams create consistent tasks with predefined content, fields, and checklists. Jira work item templates are useful for recurring work, standardization, and faster task setup.

How to Save an Existing Jira Work Item as a Template?

You can do this using apps like Smart Templates. Open the work item, click on the template menu, and select “Save as Template” to reuse its structure and content later.

What’s the Difference Between Checklists and Jira Work Item Templates?

Checklists are used to list actionable steps inside a single work item, while work item templates define the overall structure and content of a task. Templates can include checklists, but are not limited to them.

Can I Create Templates for Epics With Child Work Items?

Yes, with Smart Templates, you can create epic templates that include a hierarchy of tasks and sub-tasks. These can be reused to launch full project setups or structured workflows.

How to Add a Checklist to Work Item Templates in Jira?

To add a checklist to a Jira work item template, use Smart Checklist together with Smart Templates. Insert the checklist into the Smart Checklist area of your work item before saving it as a template.

Why Use Work Item Templates in Jira?

Work item templates save time, reduce errors, and bring consistency across projects. They’re especially helpful for repetitive tasks, onboarding, compliance, and scaling team processes. Teams that apply templates consistently are more efficient. 

Does Jira Have Work Item Templates?

Jira does not include full-featured work item templates natively. However, you can clone work items or use Automation for Jira as a workaround. A more convenient option is finding a dedicated app on the Atlassian marketplace. We recommend trying Smart Templates for Jira. The app allows you to create and manage various work item templates in Jira, from work item descriptions to an epic with subtasks saved as a template.

How to Create an Epic Template in Jira?

Use Smart Templates to create an epic template with child work items (tasks and subtasks). Start by creating an epic with linked tasks, then save the entire structure as a template to reuse in future projects.

Where to Find a List of Work Item Templates in Jira?

Template lists are available inside the Smart Templates panel. From there, you can manage, apply, or edit existing Jira work item templates. You will also see the list of all work items created from each template.

What Is the Best Tool for Jira Work Item Templates?

Smart Templates by TitanApps is one of the top tools for creating, saving, and automating work item templates in Jira. It’s helpful for templatizing both individual tasks and complex work item hierarchies. The app works with Jira Cloud and Jira Data Center, and the pricing is affordable and flexible.

Where Can I Create Work Item Templates in Jira?

You can create work item templates inside any Jira work item view (issue screen) if you have Smart Templates installed. Open the template menu from the work item view. Then, save the current work item as a template or create a new one from scratch.

How Can I Create Templates for Work Items?

To create templates for work items, define the structure you want in a Jira task. Add fields, work item description, assignees, variables, and so on. Then save it using the Smart Templates add-on to reuse this work item structure across similar work.