What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira/Jira Issue Template
Jira Cloud

Jira Issue Template: How to Make Every New Ticket Start the Same Way

In most Jira Cloud sites there's no list of saved issue templates to pick from when you click Create. (Jira now calls issues work items, which is why the menus look different from older guides.) You can still get the same result natively, in a few ways, each suited to a different kind of ticket.

Pick the route that fits who creates the ticket

You want Use Watch for
Reporters to drop a structure into the description themselves A block template: type / in the description and pick it Block templates can only be created and managed in Confluence. You can insert them in Jira, but not build them there.
The Create screen to show the structure before anyone types A custom paragraph field with a default value Company-managed projects can't set a default on the system Description field itself. Atlassian's workaround copies the custom field into Description when the ticket is created.
A full ticket with sub-tasks, labels and fields set, reused often A model ticket you clone: open it, click ⋯, then Clone The clone's summary starts with "CLONE", and it can bring along links and values you didn't mean to copy. Check before saving.
Tickets created by a form, email or integration to get the structure An automation rule that edits the description on create It fills in after the ticket is saved, so a person on the Create screen never sees it. Best for tickets no human types.
Real saved templates on the Create screen, per project and work type A Marketplace issue template app Several exist. Compare them on your own Jira plan, and check what your admin allows before you buy.

Fill the description automatically when a bug is created

For tickets arriving from a form, an email channel or another system, an automation rule is the native way to stamp the structure on.

  1. 1

    Open automation for the project

    Project settings Automation Create rule

    Admins can also create global rules that cover several projects at once.

  2. 2

    Trigger on creation

    Choose Work item created as the trigger.

  3. 3

    Add conditions

    Add a field condition so the rule only runs for the Bug work type, and a second one so it only runs when Description is empty.

    Watch for: skip the empty check and the rule wipes out whatever the reporter typed.

  4. 4

    Set the description

    Add Edit work item fields, choose Description, and paste the structure below. Save the rule, turn it on, and create a test bug to check the result.

A bug report structure to paste in

Use these headings as the text of your block template, field default or automation rule. Short headings get filled in. Long instructions get deleted. For stories, swap them for Who it's for, What they need, Why, and Done when.

  • What happened

    One sentence, in the reporter's words.

  • What should have happened

    One sentence. Half of all "bugs" turn out to be a difference of opinion here.

  • Steps to reproduce

    Numbered, starting from somewhere a developer can get to, such as a logged-in account page.

  • Where

    Browser or app version, environment (production or staging), and the account or customer affected.

  • How often

    Every time, sometimes, or once. It decides whether anyone can reproduce it at all.

  • Evidence

    A screenshot, a screen recording or a link to the log line.

Where Jira templates go wrong

The automation rule overwrites what the reporter wrote

How you'll know: Bugs that people typed carefully end up with nothing but empty headings.

Fix: Add the "Description is empty" condition, or have the rule append the structure below the existing text instead of replacing it.

Nobody uses the block template

How you'll know: It exists in the gallery, but new tickets still arrive with one line.

Fix: People don't know to type /. Name it something obvious, like "Bug report", and put it in the help text for the Description field. If it's still ignored, the default-field route puts the structure in front of them without asking.

The clone source drifts

How you'll know: Someone edited the model ticket while working on it, and every clone since has their notes in it.

Fix: Keep model tickets in a separate project or a status no one works in, and restrict who can edit them.

Every ticket is complete in structure and empty in detail

How you'll know: The headings are all there, but "Steps to reproduce" says "see email".

Fix: A template can only ask. When most bugs come from customers through a helpdesk, the detail already exists there, and it's better carried over than retyped.

Project templates, and tickets that should arrive filled in

Jira also has templates one level up. When you create a project, Jira asks you to pick one, such as Scrum (a backlog and sprint board), Kanban (a continuous flow board) or Bug tracking, and each sets up its own board, work types and workflow. That gets the structure right on day one. The first epics and stories still get typed out of the scope document.

Helpdesks such as Zendesk and Freshdesk already have native Jira integrations that create a linked Jira issue from a support ticket. What they don't do is sort a back-and-forth support thread into a bug report, so a developer still reads the whole conversation to find the steps. n-frames fills the structure above from the support conversation itself, with the steps, environment, affected account and screenshots each in their place, so the bug can be worked without opening the helpdesk. Rules inside Jira stay in Jira automation, and the connection to the other system goes through the Jira API.

Questions people ask

Does Jira have issue templates?

Not as a saved-template picker on the Create screen in most Jira Cloud sites. Natively you have block templates you insert into the description, default values on custom fields, cloning a model ticket, and automation rules that fill fields on creation. Marketplace apps add true saved issue templates.

How do I create a ticket template in Jira?

Decide who creates the tickets first. For people typing them, build a block template in Confluence and insert it with / in Jira, or set a default on a custom paragraph field. For tickets from forms or integrations, use an automation rule with the Edit work item fields action. For whole tickets with sub-tasks, clone a model ticket.

Can I set a default template when creating a Jira project?

Yes. Creating a project starts with a template choice, such as Scrum, Kanban or Bug tracking, and each sets up a different board, set of work types and workflow. That's separate from templates for the tickets inside the project.

Is there a bug report template in Jira?

The Bug work type exists by default, and the Bug tracking project template sets it up for you, but it doesn't come with a filled-in description structure. Paste the bug report structure on this page into a block template, field default or automation rule.

Can I set a default description in Jira?

Not on the system Description field in company-managed projects. Atlassian's documented workaround is a custom paragraph field with a default value, copied into Description by a post function on the workflow's Create transition. An automation rule is the other common route.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.