No issue templates in Jira (only project templates)? Our 2026 answer

[#1]

It's the most-requested thing Jira has never built: a real issue template engine for the create screen. Project templates shipped years ago. Issue templates never did. For 14 years the gap has been filled by Marketplace apps, and the category is now crowded: a dozen-plus vendors, one incumbent at nearly 5,000 installs, and a long tail of smaller players. Most of them are competent. Some of them are painful to use.

I'm Simon from NGPILOT. We entered this market in February 2026 with Modern Issue Templates for Jira, and today we're shipping its biggest update yet — Standard + Advanced editions, conflict detection, and a stack of reliability work. What follows is what Jira actually ships, what the Marketplace has filled in, where the field still hurt, and what we ended up building.

---

What Jira ships natively — and the gap it never filled

Jira ships project templates. When you spin up a new project, you can pick Scrum, Kanban, Bug Tracking, Product Management, and so on, and Jira configures the schemes, boards, default issue types, and workflows for you. That's project-level scaffolding, and it works.

What Jira has never shipped is issue templates — pre-filled content on the issue-create screen for summary, description, and the surrounding fields. Every time a developer opens Create in Jira, the form starts blank, no matter how many times the team has asked for the same structured bug report or RFC. The create-issue screen has been a blank slate for 14 years.

That's the gap. Marketplace apps have filled it since 2012.

---

What the existing apps have

The category is mature. Numbers from our own marketplace crawl, July 2026 — no commentary on the vendors, just the data:

App	Vendor	Installs	Rating	Reviews
Issue Templates for Jira	Deviniti	4,873	3.91★	125
Default Values for 'Create Issue' screen	Big Fig Tree	2,527	4.09★	26
Issue Templates Agent	Appsvio	2,253	4.74★	49
Easy Issue Templates for Jira	AppLiger	2,111	4.38★	79
Issue Templates Pro	Narva Software	2,103	4.17★	53
Templating.app	Seibert	1,167	4.82★	76
Smart Issue Templates	AppsDelivered	394	4.87★	56

The market leader, Deviniti, has been there since the start. It owns the enterprise tier with full hierarchy templates (epic → story → subtask), multi-repository, and reports. Its 3.91★ reflects a familiar pattern in mature apps: features shipped faster than the UX could absorb them, and "too complex to set up" recurs in the reviews. Appsvio (4.74★) and Seibert's Templating.app (4.82★) are the modern Forge-native challengers with clean implementations. AppLiger, Narva, AppsDelivered, and a dozen others each take a reasonable slice.

None of them are bad. The category works, mostly. But when I read the 1- and 2-star reviews of the leaders, four complaints kept showing up:

1. "Templates stopped working after a reinstall." UI Modifications entries live on Jira's side; template records live in app storage. When those two drift, auto-apply silently fails. Most apps don't reconcile.
2. "Two templates fight over the same project/issue-type." Jira's UI Mods API only allows one template to own auto-apply per project × issue-type context. Most apps pretend that constraint doesn't exist and let the entries race each other on the create screen.
3. "I had to re-author templates from scratch." Few apps support any kind of import. Almost none support GitHub or Markdown.
4. "Setup took hours." Heavy UIs, multi-step configuration, no starter content.

That's the field we entered.

---

Why we built another one

Four things mattered to us, and no single app had all four.

Forge-native from day one. No Connect-era code, no hybrid migration, no external database. Templates live in Forge storage; auto-apply runs through Jira's UI Modifications API. The only network calls out of the Atlassian infrastructure go to GitHub when you import a template.

GitHub/Markdown import with YAML frontmatter. Paste a URL to a .github/ISSUE_TEMPLATE/bug_report.md file or a Gist, fetch, and the markdown converts to rich text. YAML frontmatter is parsed — name, title, labels, assignees map onto the template fields automatically. JSON export covers the other direction, for backup or sharing templates across instances.

Multi-field pre-fill via UI Mods. Templates can declare a fields map that pre-fills labels, duedate, priority, components, fixVersions, versions, assignee, reporter, and environment at create time. Most other apps stop at summary and description; we extend the same auto-apply path to the rest of the create dialog.

Conflict-aware assignment. Jira's UI Modifications API registers one context per project × issue-type pair — only one template can own auto-apply for any given context. We made that constraint explicit. When you assign a template to a context another template already owns, a conflict dialog lists the clash before the prior template is disabled; the loser gets a warning-tinted row and a one-click re-enable.

---

What we have, what they don't

I want to be honest about both directions. Here's the head-to-head against the top three by installs. Feature data from each vendor's Marketplace listing and our March 2026 competitive analysis; install and rating data from our July 2026 marketplace crawl:

Capability	Modern Issue Templates (NGPILOT)	Deviniti	Appsvio	AppLiger
Forge-native (no Connect)	✅	❌ (hybrid)	✅	✅
Free up to 10 users	✅	❌	✅	✅
Template CRUD + rich-text editor	✅	✅	✅	✅
Auto-apply via UI Modifications	✅	✅	✅	✅
Variables + inline validation	✅	✅	✅	✅
GitHub / Gist / Markdown import	✅	❌	❌	❌
YAML frontmatter parsing	✅	❌	❌	❌
JSON export / backup	✅	❌	✅	❌
Multi-field pre-fill (labels, duedate, priority, …)	✅ Advanced	✅	—	—
Conflict detection (1 context = 1 owner)	✅	❌	❌	❌
Orphan UIM reconcile-on-load	✅	❌	❌	❌
Application log (filter, export, 7-day retention)	✅ Advanced	✅	✅	❌
Starter Template Library	✅ (22)	✅	✅	—
Hierarchy templates (epic → story → subtask)	❌	✅	✅	✅
Multi-repository	❌	✅	❌	❌
Jira Automation / REST API integration	❌	✅	✅	❌
Reports / analytics	❌	✅ Advanced	✅ Audit	❌
Cloud Fortified	❌	✅	✅	✅
Installs (July 2026)	1	4,873	2,253	2,111
Rating / reviews	—	3.91★ / 125	4.74★ / 49	4.38★ / 79

A few things to call out honestly:

Hierarchy templates (epic → story → subtask from a single template) — Deviniti, Appsvio, and AppLiger all have it. We don't. It's on the roadmap, but it's a real gap today, and if you need it, those vendors are the right answer.

Jira Automation / REST API integration — Deviniti, Appsvio, and Narva expose templates to Automation rules and external scripts. We don't. Templates only fire on the standard create-issue screen.

Cloud Fortified — Deviniti, Appsvio, AppLiger, and Narva all have it. We don't yet; we haven't been on the Marketplace long enough to apply.

What we have that the others don't:

• GitHub/Gist/Markdown import with YAML frontmatter — nobody else in the matrix does GitHub specifically. Appsvio has generic template import/export, not source-control integration.
• Conflict detection with disabled-assignment lifecycle — no other app in the field surfaces the "one owner per project × issue-type" constraint explicitly. Most let two templates fight silently.
• Three layers of orphan UIM prevention — read-path self-healing, write-path overlap deletion, and reconcile-on-load — so templates don't break silently after a reinstall. The "templates stopped working after reinstall" complaint in the leader's reviews is exactly what this prevents.

---

On Cloud Fortified, and a tradeoff we're weighing

The matrix marks us ❌ for Cloud Fortified. That's accurate today, and it's the gap we're explicitly working toward — Cloud Fortified, the Runs on Atlassian signal, and the broader enterprise security posture all reward apps that keep every byte of customer data inside Atlassian's infrastructure.

Most of our app already qualifies. Templates, auto-apply, the editor, variables, conflict detection, the application log — all of it runs inside Forge with no calls outside Atlassian. The one exception is GitHub import, which makes outbound calls to api.github.com and raw.githubusercontent.com to fetch templates.

So we're weighing a real tradeoff. GitHub import is one of our most-differentiated features — nobody else in the matrix does it, and teams that keep templates in .github/ISSUE_TEMPLATE/ get genuine value from pulling them in directly. But it's also the only thing standing between us and a fully closed egress surface, which is what enterprise security reviews (and Cloud Fortified) want to see.

The direction we're leaning: remove GitHub URL import, keep Markdown and JSON file upload (which parses files in-browser with no network calls), and ship the zero-egress version as the next major release. That puts us on the direct path to Runs on Atlassian and Cloud Fortified without giving up the markdown-import workflow entirely.

If you're evaluating the app for an enterprise rollout and GitHub import is the reason you'd trial — tell us. The tradeoff is real and we haven't locked the decision.

---

What you can verify in a five-minute trial

If you install the app, here's what to look at:

• Starter Library — 22 curated templates across Software Engineering, Operations, Product, Team & People, General. Several ship with fields already configured (Bug Report auto-tags bug; Sprint Retro Action Item sets a 7-day due date via {{today+7d}}). A new install can go from zero to twenty-two templates in two clicks.

• Variables with inline validation — {{currentUser}}, {{projectKey}}, {{today+7d}}. Typos get a red wavy underline with a "Did you mean?" suggestion; unresolved variables render as ⚠️[unknown:name] so failures are visible instead of silent.
• Rich-text editor + inline editing — Tiptap-based, code blocks with syntax highlighting. Click any summary or description cell in the table to edit in place — no modal needed for a one-line fix.
• Conflict detection — assign two templates to the same project × issue-type. You'll see the conflict dialog before the prior template is disabled; re-enable runs the same check symmetrically.

• Application log (Advanced) — 50 entries, status filter, CSV export, 7-day retention. Answers "why didn't my template apply?" without making you open a browser console.

Two editions on the Marketplace. Standard (incl. free ≤10 users) covers templates, GitHub/Markdown import, Starter Library, variables, multi-project assignment, and conflict detection. Advanced adds multi-field pre-fill config and the application log. Trials unlock everything.

---

Where we are

Modern Issue Templates for Jira is still new — 1 install, 0 reviews as I write this. The point of this release isn't a victory lap. It's to say: the category works for most teams, the leaders are mature, and we'd rather be the app that ships conflict detection and a 7-day application log than the one that ships another themes panel.

If you administer Jira and you've ever been hit by an issue-templates app that "stopped working" after a reinstall, or that let two templates fight over the same bug context, give it a try and tell us what's missing.

• Modern Issue Templates for Jira

---

Pair it with diagrams where templates aren't enough

Issue templates standardize the shape of an issue. Plenty of teams also need to standardize the shape of a discussion — an architecture sketch in an RFC, a flowchart in a runbook, a sequence diagram in a postmortem. We ship two Forge-native Jira apps for that, depending on how you think:

• Mermaid Plus Diagrams for Jira — for code-first diagrams. Write Mermaid syntax (sequence, flowchart, Gantt, class), get a rendered diagram inline. Good for technical documentation where the diagram is source.

• Excalidraw Diagrams plus Whiteboards for Jira — for visual sketches. A full Excalidraw canvas inside the Jira issue panel, with 229 bundled shape libraries (AWS, Azure, GCP, UML, networking) and an offline-first model. Good for architecture drawings, wireframes, and the kind of informal thinking that doesn't belong in a formal diagram.

Same Forge-native ground as the templates app. Different medium.

What's the worst template-related behavior you've run into — silent failures, conflicting templates, lost configs on reinstall? I'd genuinely like to hear it, because the v1.3 release was largely shaped by reading the 1- and 2-star reviews of the incumbents.

— Simon from NGPILOT