Issue Templates for Jira Cloud is now Process Templates for Jira

If you installed our app as Issue Templates for Jira Cloud, you may have noticed a new name on your Marketplace listing. The app is now called Process Templates for Jira (Issue Templates & Epics).

Before anything else, the part that matters most: this is a rename, not a migration. Same app, same data, same install, same pricing. Your templates, your settings and your history are exactly where you left them, and there is nothing you need to do. The reviews carried over too, so the feedback from teams who already use it stays attached to the app under its new name.

So if nothing functional changed, why rename it at all? Because the old name had stopped describing what the app actually does.

Why we changed the name

“Issue Templates” describes prefilling a single issue: one ticket, the right fields, ready to go. That is a real and useful job, and the app still does it. But it is a small part of what the app is really for.

What teams tell us is consistent. They are not templating one issue. They are templating a whole process. An epic with its stories and sub-tasks, saved once and launched as a complete tree whenever the work repeats. Employee onboarding. Incident response. Recurring requests and work orders. Campaign launches. The structure that recurs is a process, and the app’s real strength is saving that whole structure and relaunching it in one click.

“Issue Templates” undersold that. It made the app sound like single-ticket prefill when its centre of gravity had moved to repeatable, multi-issue processes. The new name says what the app is for: turning a repeatable process into one reusable template.

The parenthetical, “(Issue Templates & Epics)”, is deliberate. Issue templates are still part of the story, and epics with their hierarchies are the structure that makes process templating work. The name now leads with the outcome and keeps the familiar terms close behind.

What this means if you already use the app

In practical terms, nothing changes for you.

Your existing templates work exactly as before. Single-issue templates, epics with sub-tasks, variables, smart values, permissions, the dashboard gadget, JQL search by template, all of it is unchanged. The app behaves identically. The only difference is the name on the listing and a refreshed look that reflects the process focus.

Pricing is unchanged: free for up to 10 users, then 0.50 USD per user per month, with a 30-day trial. Your billing, your trial status and your user count carry over untouched.

And to be explicit about the things people worry about during a rename: you do not need to reinstall, you will not lose your templates, and your reviews and install history moved with the app. There is no action required on your side.

What the app stands for now

The rename comes with a sharper idea of who the app is for and what it does best.

Process Templates for Jira is for the people who run a process, and works alongside the Jira administrators who govern it. The HR lead who owns onboarding. The support manager who owns incident response. The operations or marketing lead who runs the same launch every time. The model we are building around is simple: process owners build and launch their own templates, while administrators keep governance over who can create and manage them. Owner-run, admin-governed.

That is the direction. Capture a repeatable process once as an epic with its full hierarchy, fill in the few things that change as variables, and relaunch the whole structure in a click whenever the process comes round. You can see the full feature set on the features page, browse ready-made structures in the template library, or read the how-to guide to set up your first one.

Same foundations underneath

None of the trust foundations changed with the name. Process Templates for Jira is built on Atlassian Forge, is Cloud Fortified, and stores its data on a dedicated backend we host in EU data centres in Frankfurt, with no personal data retained. The security posture, the hosting and the data handling are exactly as they were.

Nothing to do, but worth a look

There is no action required. Your app keeps working under its new name. But if “Issue Templates” had you thinking of it as single-ticket prefill, this is a good moment to look again at what it does at full stretch: saving an entire process and launching it in one click.

If you have not installed it yet, you will find it on the Atlassian Marketplace as Process Templates for Jira, free for up to 10 users with a 30-day trial above that.

Same app you trusted as Issue Templates. Clearer name for what it actually does.