Issue Templates for Jira Cloud turns any Epic, Story, Task or Sub-task into a reusable template. Wrap fields in variables your users fill at create time. Launch from the issue menu, a dashboard gadget, or the create-issue screen.
30-day free trial · free up to 10 users · no credit card.
What it creates
Apply this template, get the whole onboarding hierarchy in Jira.
Used by 400+ teams across software, IT, HR and customer service, on Jira Cloud and Jira Service Management. 4.6★ (20 reviews)
Cloud FortifiedLoved on the Atlassian Marketplace
Real teams, real Marketplace reviews.
“We started to use Issue Templates for Jira a few weeks ago and it was a game changer. It improved our Jira experience as a team and allowed non-developer users to create issues too: bugs, feature requests, even ideas for the future. Having a place where we can ensure conformity and produce a standard result is excellent.”
“We handle a lot of recurring work orders where the structure is always the same, only the scope changes. This app lets us create templates so we don't have to dig up old ones and adapt them every time.”
“Being able to template the planning steps has eliminated multiple meetings and emails per event, giving time back to myself, my team and my entire reporting chain.”
Template library
Browse, search and favorite every reusable template, grouped by project, with the full issue hierarchy a click away. Stop hunting for that one ticket to clone.
What you can template
Issue Templates copies what your tickets already look like, then lets you replace any value with a variable so users fill it in at create time. Templates and tickets stay in sync without manual upkeep.
Every Jira issue type, plus Service Management requests.
Parent + child templates. Sub-tasks inherit variables from the parent.
Text, dropdowns, multi-select, dates, user pickers, all templated.
Free-text, dropdown, date. Define once, reuse across the whole template.
Fill date and user fields at launch, like the assignee or a due date a few days out.
"Relates to", "Blocked by", "Duplicates". Preserved between template-created issues.
Native support for the Tempo Account custom field, prefilled per template.
Defaults set on the template, optionally overridable at creation time.
How it works
Right-click any Jira issue, choose Save as template. Issue Templates copies every field, attachment and sub-task. Done. No new screen, no setup.
Wrap the variables your users will fill in: customer name, due date, environment, severity. Choose text, dropdown or date. Variables are reusable across the parent and every sub-task.
Your team picks a template and fills in the variables. Issue Templates can skip or prefill the standard Jira create screen, or create the issue directly. A template with sub-tasks creates the whole hierarchy in one launch.
What it does
Variables, full sub-task hierarchies, a dashboard launcher, and JQL search by template, none of which native Jira templates can do.
Variables
Wrap any field in a variable. Text, dropdown, date. Your users fill it in at create time, the template structure stays consistent across every ticket your team launches.
Build a template once with its full sub-task list. One launch creates the parent and every child, with variables propagated through the whole tree.
Add the Issue Templates gadget to any Jira dashboard. One click on a template, fill in the variables, ticket created. No menu diving.
A JQL function finds every issue created from a given template, so you can build saved filters, dashboards and reports around the templates your team relies on.
Anatomy of a template
Every template is built from three layers: the bits that never change, the bits the user fills in, and the bits Jira computes. Together, they let one definition turn into hundreds of consistent tickets.
The shape your team always wants: which fields are present, which sub-tasks chain underneath, which issue links carry across.
The bits that change per ticket. Wrap any field in a variable: text, dropdown or date. Reuse the same variable across the parent and every sub-task.
Date and user fields that fill themselves in at launch. Set the assignee to whoever creates the ticket, or a due date a few days out. Jira computes them, nobody types them.
user() plusDays(now(), 10) now() Composed
One template definition. Your team fills the variables; Jira computes the date and user fields. The ticket below is what gets created: the variables your team typed, plus smart values filled in automatically.
Use cases
Software, IT, customer service, HR. Anywhere your team creates the same shape of ticket more than once a month, Issue Templates pays for itself in the first sprint.
Software development
A Bug template with Steps to Reproduce, Expected, Actual, Environment. A User Story template with Acceptance Criteria. Every dev writes the same shape of ticket without thinking about it.
See the templateIT service management
VPN access, software requests, admin access, incident report. Template once with the right approvers, fields and security level, launch every time the request comes in.
See the templateCustomer service
Customer onboarding Epic with all its sub-tasks. Customer feedback template with the questions you actually want answered. Every customer interaction goes through the same playbook.
See the templateHR operations
Employee onboarding with the laptop request, the access provisioning, the welcome session. Offboarding with the inverse. Recruitment with the interview loop. Templated, repeatable, auditable.
See the templateWhy teams choose us
Built on Atlassian Forge and Cloud Fortified, with template data stored in the EU (Frankfurt) and no personal data retained. We also take part in the Atlassian Marketplace Bug Bounty Program.
Simple to learn. Save your first template from any existing Jira issue in a click, with no technical setup and no dedicated admin project to configure.
Works natively inside Jira Cloud and Jira Service Management, with a dashboard gadget, JQL search by template, Jira Automation support and the Tempo Account field.
Free for up to 10 users, then 0.50 USD per user per month on your standard Atlassian invoice. Every paid plan starts with a 30-day free trial.
Why teams switch
Re-typing the same fields kills momentum. Issue Templates locks the structure once, then your team launches consistent tickets in seconds, not minutes.
Pick any existing Epic, Story, Task, Bug or Sub-task in your project and turn it into a template. No re-typing fields, no second tool to manage. The template inherits everything that was on the source.
Wrap any field in a variable and your users fill it in at creation time. Text inputs, dropdowns, date pickers. Reuse the same variable across the parent issue and every sub-task in one go.
The app lives where Jira users already are. Project sidebar, dashboard gadget, and the create-issue prefill. No new dashboard to log into, no new menu to learn.
Built on Atlassian's Forge platform with the Cloud Fortified badge. Atlassian-attested security and GDPR-aware handling, with template data stored on a dedicated EU backend (DigitalOcean, Frankfurt).
Native Jira vs Issue Templates
Jira lets you set default field values per project. That's not templates. There's no reusable issue blueprint, no variables, no dashboard gadget, no whole-hierarchy launch. Issue Templates fills those gaps without leaving Jira.
Wondering how we compare to Deviniti or Smart Templates? 10x easier to learn, per our customers.
See every featurePricing for every team size
Free
$0 up to 10 users
Every feature, capped at 10 users on your Jira site. No credit card.
Team
$0.50 per user / month
More than 10 users, billed on your monthly Atlassian invoice. 30-day free trial.
Per-user pricing drops as your team grows.
FAQ
From the blog
Build a Jira bug-tracking workflow from intake to verified fix: statuses, severity vs priority, triage, SLAs, root-cause analysis and automation.
Read article
Manage test cases in Jira natively: a dedicated issue type, reusable templates, traceability to stories and bugs, and test cycles, no extra QA tool.
Read article
ITIL-aligned ITSM best practices on Jira Service Management: SLAs, incident, problem, change and request management, plus templates for consistency.
Read article
Cloud Fortified is Atlassian's highest trust tier for Marketplace apps: security, reliability, and support audited on an ongoing basis. What it covers.
Read articleFree up to 10 users, 30-day trial
Install Issue Templates in two clicks. No credit card. Join 437+ teams already templating smarter.