Quick Issue Templates for Jira

Documentation & support

What this app does

Save any issue as a reusable template — summary, description, labels and sub-tasks — then create that issue again in one click, in any project you have access to.

Templates are stored inside the app. You do not need to create a separate Jira project to hold them, and you do not need to maintain one.

Getting started

Install the app from the Atlassian Marketplace.
In Jira, open Apps → Templates in the left sidebar.
Click New template.
Give it a name, choose the project and issue type, then fill in the summary, description, labels and sub-tasks you want every copy to start with.
Click Save.
Back on the list, click Create issue next to any template. The issue and all of its sub-tasks are created immediately, and the new issue key is shown.

Using placeholders

Anywhere in the summary or description you can write a placeholder in double braces, for example {{customer}} or {{release}}. Placeholders you do not fill in are left in the text exactly as written, so nothing is silently lost.

Frequently asked questions

Do I need a separate project to store templates?

No. Templates live inside the app's own storage on Atlassian's infrastructure. Nothing extra to create, nothing extra to clean up.

Can one template be used in more than one project?

A template names the project it creates issues in. To reuse the same content elsewhere, export your templates, change the project key, and import them back — or duplicate the template and pick a different project.

Who can see and use the templates?

Templates are shared across everyone who can open the app in your site. Issues are always created as you, through Jira's own permission checks — the app can never create something you could not create yourself.

Why did my label change?

Jira does not allow spaces inside a label, and rejects the whole issue if it finds one. Rather than fail your request, the app converts spaces to hyphens: needs review becomes needs-review.

Can I back up or move my templates?

Yes. Export gives you plain JSON containing every template. Import reads the same format back. There is no lock-in and no proprietary file type.

What happens if a sub-task fails to create?

The parent issue is still created and kept. Each sub-task is attempted separately, and the app tells you how many failed rather than losing your work.

Which Jira products are supported?

Jira Cloud. The app is not available for Jira Server or Data Center.

Current limitations

These are known and deliberate for the current version:

Templates set summary, description, labels and sub-tasks. Custom fields are not yet supported.
Sub-tasks are created one level deep, under the issue the template creates.
The project a template belongs to must have a sub-task issue type enabled for sub-tasks to work.

If any of these blocks you, please say so when you contact support — what people ask for is what gets built next.

Privacy and data

The app runs entirely on Atlassian's infrastructure. Your templates and your Jira data are never sent to any external server, and the app makes no outbound network calls.

Support

Email: support@kelvido.com

Please include your Jira site URL, the template name, and what you expected to happen.

Replies usually arrive within one business day.