Skip to content
Get the extension

Getting started

Install the extension, create your first template, and insert it in a Jira ticket — under five minutes.

Updated April 29, 2026

This is the fastest path to value. By the end you’ll have one custom template and you’ll have inserted it into a real ticket field.

1. Install the extension

Pick the store that matches your browser:

Click Add to Browser (or Get / Install). Your browser will ask you to confirm that the extension can “Read and change all your data on all websites” — this sounds broad, but it’s required so the extension can detect Jira, Azure DevOps, Trello, and Asana pages and inject templates into their editors. No data ever leaves your browser.

2. Check your allowed domains

Important: The extension only activates on websites whose URL matches its domain whitelist. The defaults are jira, trello, atlassian.net, dev.azure.com.

If your Jira or Azure DevOps instance runs on a custom domain (e.g. jira.yourcompany.com), you need to add it now — otherwise the extension won’t appear on your pages.

Open the Settings panel (gear icon) on the options page and find the Allowed domains field. Add your domain as a comma-separated entry, e.g. jira,trello,atlassian.net,dev.azure.com,jira.yourcompany.com. See Settings for details.

3. Open the options page

If you haven’t already, click the extension icon in your browser’s toolbar. The options page opens in a new tab — this is where you manage every template.

The options page on first launch — three default templates are pre-loaded so you have something to work with.
The options page showing a list of three default templates.

You’ll see three pre-loaded templates: a story, a bug, and an example comment. They demonstrate the structure; feel free to delete or edit them.

4. Create your first template

  1. Click Add new template at the bottom of the list.
  2. Give it a name (this is the label that shows up in dropdowns and buttons).
  3. Pick the issue type — Story, Bug, Task, Epic, or anything you type yourself.
  4. Leave the projects field blank to apply the template to every project, or enter a comma-separated list of project keys (e.g. ABC, BCS) to scope it.
  5. Type your template content in the editor. Both rich text and wiki markup are supported.
  6. Save (Ctrl+S, or it auto-saves after 250 ms).
The editor. The right pane shows a live preview when you're authoring wiki markup for Jira Server.
The template editor with a rich text content area, name field, issue type, and projects fields.

Tip: You can leave the issue type blank if you want a generic template that works for everything in a project.

5. Insert the template in a ticket

Open any Jira create-issue dialog or work item form. Three insert methods are available — pick whichever feels fastest:

  • Quick-access buttons — small buttons appear above the description field, one per matching template.
  • Dropdown menu — a single dropdown listing every matching template.
  • Right-click menu — right-click in the description field; templates show up in the context menu.

Or do nothing at all and rely on autofill — which we cover in the autofill chapter.

6. Done. What’s next?

Free forever. Support if it saves you time.

This extension has been maintained for over five years. If it has saved you a few hours of typing, consider supporting development — every contribution makes a difference, and two channels exist so you can pick the one you prefer.

See ways to support