Frequently asked questions

What is a Jira template?

A Jira template is a predefined Jira issue that you save as a model for future issues. It captures the shape of the source issue (fields, sub-tasks, links, default values) and exposes optional variables your users fill in at create time. Launching the template produces a fresh, real Jira issue with the template applied.

What happens if I uninstall the app?

Existing issues that were created from templates remain untouched. They are normal Jira tickets and stay in your project exactly as they were. What you lose is the ability to manage existing templates or create new tickets from them. Reinstalling restores access without data loss because your template definitions are kept on our DigitalOcean backend in Frankfurt (EU).

Do you support custom fields?

Yes. Process Templates for Jira supports the full set of standard Jira custom-field types: text (short and long), single-select, multi-select, cascading select, dates, datetimes, user pickers, group pickers, URL fields, labels, radio buttons and checkboxes. The Tempo Timesheet Account field is also supported natively.

Can I reuse variables across sub-tasks or Stories under an Epic?

Yes. A variable defined on a parent template is automatically available to every sub-task or child Story underneath it. When the user fills the variable on the parent issue at create time, the value propagates to every child, so the whole templated tree stays consistent.

Can I create an issue from a Jira dashboard?

Yes. The app ships a dashboard gadget. Add it to any Jira dashboard, surface the templates your team uses most, and your users launch tickets in one click without diving into a project menu. See the dashboard gadget walkthrough.

Do I need a dedicated project for templates?

No. Templates can live in any existing project. The source of a template is just a normal Jira issue, in any project your team already uses. Templates can also be scoped globally if you want them available across all projects.

Do you store personal data?

No. The app stores only the template metadata required to make templates work (field definitions, variables, sub-task structure). It does not store personal data about your users. See the privacy and security guide for details on what is stored, where, and under which controls.

Where is data stored?

Template data is stored on a dedicated backend we host with DigitalOcean in EU data centres in Frankfurt, Germany.

How much does the app cost?

Free for up to 10 users on your Jira site. Above 10 users, the price is 0.50 USD per user per month, billed via the Atlassian Marketplace alongside your other Cloud apps. There is a 30-day free trial on every paid plan, no credit card required. Volume discounts apply at 100, 250 and 1,000 users per Atlassian’s standard per-tier pricing model. See the pricing page for the current details.

Does it work with Jira Service Management?

Yes. Templates fully support Jira Service Management request types, security levels and request channels. You can template incident reports, service requests, access requests, and the rest of your JSM intake.

Can I trigger a template from Jira Automation?

Yes. The app exposes an HTTPS endpoint that Jira Automation can call via the Send Web Request action. Combine this with any Automation trigger (scheduled, event-driven, manual) to fire a templated ticket without human intervention. See the Automation integration walkthrough.

Refresh your browser first. If the app entry is still missing, check that the Atlassian user you signed in with has at least project admin permission on the project you opened. App actions are only surfaced to users with sufficient permissions. If it still does not appear after a successful install, open a ticket on the support portal and we will help you track it down.