Eriksen Labs

Jira issue template generator

Choose an issue type, keep the sections your team uses, and copy a description that pastes into Jira with its headings, lists and checklist. Free, it runs in your browser, and nothing you write is sent anywhere.

Free, no sign-up Runs in your browser Bug, Story, Task, Incident, Spike, Epic

Issue type
Team style

What most teams ask for.

Preview

Bug

[Area]: [what goes wrong] when [action]

Priority
Medium
Labels
needs-triage

Description

Steps to reproduce

  1. Go to [page or screen]
  2. [Do this]
  3. [Then this]

Expected result

[What should have happened]

Actual result

[What happened instead. Copy any error message exactly.]

Environment

  • Version or build:
  • Browser or device:
  • Operating system:
  • Test account or site (never a password):

How often

[Every time, sometimes or once. If sometimes, roughly how often.]

Screenshots and logs

[Attach a screenshot, recording or log. Remove personal data first.]

Done when

  • Reproduced
  • Cause noted in a comment
  • Fix verified where it was reported
  • Test added that would have caught it

Both buttons copy the description and its checklist. Summary, labels and priority go in their own fields in Jira.

Edit the template

How to use it

  1. Choose the issue type, and a team style if Standard asks for too much or too little. Light keeps the few sections everyone fills in; Detailed adds what formal triage or review needs.
  2. Change the text to suit your team. Untick sections you do not need, add your own, and add or remove checklist items. Text in [square brackets] marks what the reporter fills in.
  3. Press Copy for Jira and paste into the Description field of a new issue. Put the summary, labels and priority in their own fields. Copy as Markdown is for tools that take Markdown, such as GitHub or GitLab issue templates.

Your changes stay in this browser, so they are still here next time. The page counts how often the copy buttons are used, by button, page and issue type, and nothing else; see the privacy policy.

What Jira Cloud does on its own

No Description default in company-managed projects

Description is a system field, and in a company-managed project Jira Cloud has no setting that gives it a default text: every new issue starts with it empty. Team-managed projects are the exception. There, each issue type can have a default description, set in the project’s issue type settings.

Defaults for custom fields

In a company-managed project, a custom field can have a default value, set per field context. Atlassian’s own workaround puts the template in a paragraph field, and a workflow post function copies it into Description when the issue is created.

Automation runs after Create

A Jira Automation rule can write a template into the description when an issue is created, but only once it exists. The person filling in the form still starts from an empty field.

No supported prefilled create links

Atlassian documents links that open the Create screen with fields already filled in for its self-managed Jira, not for Jira Cloud. On Cloud they are unsupported, so even one that works today can stop without notice.

Otherwise there is copy and paste, which works in any project, and is what this page is for. In a team-managed project you can also paste the template into an issue type’s default description. Atlassian changes Jira Cloud often, so check its documentation if one of these has changed for your site.

Want this to appear automatically in Jira’s Create dialog?

Issue Templates & Create Defaults for Jira fills in the summary, description, checklist, labels and priority from a template when someone opens Jira’s own Create dialog with one of the issue types you choose. Each field it fills carries a note saying where the text came from, and once someone writes their own summary or description, the app leaves the form alone.

To take a template from this page into the app with its formatting, paste it into an issue’s description, then, as a project or Jira administrator, choose Save as template from the issue’s ••• menu.

Submitted to the Atlassian Marketplace and awaiting approval.

About the app Documentation

Each template on its own page

With a note on what each section is for, and when to use another type instead.