Jira Issue Templates
How to create, manage, and scale issue templates in Jira Cloud — from native workarounds to dedicated apps.
Skip to comparison ↓Why Jira Cloud doesn't have built-in issue templates
Jira issue templates don't exist as a native feature in Jira Cloud — and if you moved from Jira Server or Data Center, you've almost certainly felt the gap. Jira Server had a popular marketplace app for issue templates that became deeply embedded in team workflows — from IT helpdesk to software sprints.
Jira Cloud takes a different approach. Instead of a native issue templates feature, Atlassian has focused on Jira Automation and a rich Marketplace ecosystem. The idea is that templates can be approximated through automation rules or third-party apps — but neither solution is plug-and-play for teams expecting a simple "create from template" button in the Create Issue form.
The real cost shows up over time. Teams creating issues from scratch forget to fill in critical fields — Priority, Component, Labels, Assignee. Recurring workflows (bug reports, change requests, onboarding tasks) require repetitive manual setup. New teammates don't know which fields matter. Reporting suffers because data is inconsistent across issues.
So how do teams solve this today? There are three main approaches, each with different tradeoffs.
Jira Automation rules as templates
The most common native workaround uses Jira Automation's "manually triggered" rules. You configure a rule that creates an issue with pre-filled fields, then run it on demand. It's free, built into Jira Cloud, and requires no additional apps.
How to set it up (5 steps)
- 1Go to Project Settings → Automation
Open your Jira project, navigate to Project Settings, then select Automation from the left sidebar.
- 2Create a new rule with "Manually triggered" trigger
Click "Create rule", select the "Manual trigger" option. This lets users run the rule on demand from the board or backlog.
- 3Add a "Create issue" action
Add the "Create issue" action and select the target project and issue type for your template.
- 4Pre-fill field values
Set values for Summary, Description, Priority, Components, Labels, and any custom fields your template needs.
- 5Run manually when needed
Users trigger the rule from the Automation section. The issue is created in the background with pre-filled fields.
Advantages
- Built into Jira — no extra cost or installation
- Works well for 1–3 simple templates
- Full control via Jira Automation rule conditions
Limitations
- No template picker in Create Issue — users trigger the rule separately
- No hierarchy support — each level (Epic, Story, Subtask) needs its own rule
- No dynamic variables (current date, sprint, logged-in user)
- Scales poorly — 10+ templates become hard to manage in Automation
- Best for
- Small teams with 1–3 simple templates
- Hierarchy support
- No (requires multiple rules)
- Template picker
- No
- Setup complexity
- Medium
Clone a reference issue
The simplest approach: create a dedicated "template" issue in your project, prefix its summary with [TEMPLATE], and clone it whenever you need a new issue. No setup required — anyone with Jira access can do it immediately.
To use it: open your template issue, click the three-dot menu → Clone. Edit the cloned issue, remove the [TEMPLATE] prefix, and fill in any remaining fields.
Advantages
- Zero setup — works immediately with any Jira project
- Everyone can do it without admin access
- Useful for quick one-off use with 1–2 people
Limitations
- Cloning does not copy child issues (subtasks) in Jira Cloud — you get only the parent
- Template issues pollute your backlog and board
- No automation — fields must be edited manually after cloning
- No control over which templates teams use or how often
- Best for
- Quick one-off use, 1–2 people
- Hierarchy support
- No
- Template picker
- No
- Setup complexity
- None
Dedicated issue template apps
Atlassian Marketplace has a growing selection of dedicated issue template apps — from lightweight options to enterprise-grade solutions. Unlike the native workarounds, these apps are purpose-built for the exact workflow teams expect: open Create Issue, pick a template, submit.
Here's what a dedicated template app adds over native Jira capabilities:
- Template picker in Create Issue screen
Users choose a template without leaving the Create Issue form. No automation rules to trigger separately.
- Epic → Story → Subtask hierarchy with one click
Create a full issue hierarchy — including parent/child links and relationships — from a single template. What would take 3+ automation rules happens instantly.
- Auto-fill any field with static or dynamic values
Set default values for Priority, Component, Label, Assignee, Reporter, custom fields — including dynamic values like current date, current sprint, or logged-in user.
- Role-based permissions
Control who can create, edit, and use templates. Separate template authoring (admins) from template usage (all team members).
- Audit trail and usage reporting
Track which templates are used, by whom, and how often. Essential for compliance teams (SOC 2, ISO 27001) and process governance.
- Jira Automation integration
Use "Create Issue from Template" as an action in Jira Automation rules — combine template consistency with trigger-based automation.
- Best for
- Teams at scale with recurring workflows
- Hierarchy support
- Yes — full Epic to Subtask in one click
- Template picker
- Yes — in Create Issue form
- Setup complexity
- Low (5 min per template)
Comparison: Which approach fits your team?
Here's how the three approaches compare across the criteria that matter most for Jira teams managing issue templates at scale.
| Criteria | Automation rules | Clone issue | Template app |
|---|---|---|---|
| Template picker in Create Issue | No | No | Yes |
| Issue hierarchy creation | 3+ rules per template | No | One click |
| Auto-fill any field | Limited | Manual after clone | Full support |
| Dynamic variables | No | No | Yes |
| Permissions model | Project admin only | None | Role-based |
| Jira Automation action | N/A (is automation) | No | Yes |
| Audit trail | Rule execution log | None | Full + CSV export |
| Setup time per template | 10–30 minutes | 2 minutes | 5 minutes |
| Best for | 1–3 simple templates | Quick one-off use | Teams at scale |
Frequently asked questions about Jira issue templates
Our recommendation
If your team only needs 1–3 simple issue templates and you don't require a template picker in the Create Issue form, Jira Automation rules are a reasonable starting point. They're free, built-in, and adequate for simple recurring workflows.
If you need hierarchy creation (Epic → Subtask), auto-fill of custom fields, dynamic variables, or permissions control, a dedicated template app is the right choice. The setup overhead is minimal — typically 5 minutes per template — and the ongoing time savings add up quickly.
Templify specifically is worth evaluating if you want all three capabilities together: a native template picker in the Create Issue screen, one-click hierarchy creation, and a "Create from Template" action for Jira Automation. It's built on Atlassian Forge (your data stays in Atlassian's infrastructure) and free for teams up to 10 users.
Ready to try a template app?
Templify is free for teams up to 10 users, with a 30-day trial for larger teams. Forge-native, GDPR compliant.
Learn more about Jira issue templates
Deeper guides on specific aspects of issue templates in Jira Cloud.
Jira Issue Templates: Native vs App (2026)
A detailed comparison of native Jira workarounds vs dedicated template apps, with real-world use cases.
Default Description Template Without Scripts
How to set a default issue description template in Jira Cloud without writing any automation scripts.
Jira Automation Issue Templates
Step-by-step guide to building Epic, Task, and Subtask workflows using Jira Automation rules.
Templify vs Jira Template Apps Comparison
How Templify compares to other template apps on Atlassian Marketplace across key features.
Template Governance: Permissions & Audit Logs
Best practices for managing who creates and uses issue templates across projects and teams.
5 Issue Template Examples for IT, HR, Marketing
Ready-made Jira issue template examples for common use cases across different business teams.