Datum

Apps → Prefab

A Datum app for Jirav1.0.3

Prefab

Structured Jira issue templates — pre-fill fields on the native Create screen, and scaffold whole epic→story→sub-task trees in one click.

Get it on the Atlassian Marketplace → All apps
Issue templatePrefab · SPT-118
Summary Pre-filled from template Set
Hierarchy Epic → story → sub-task Scaffolded
Fields Priority, labels, custom fields Set
One click on Jira's native Create screen — no second app to learn.

The problem

Every team has issues that arrive malformed — missing fields, wrong priorities, no structure — and 'create from template' usually means a second screen, a separate app, or nothing at all. Whole hierarchies of epic → story → sub-task get rebuilt by hand, issue after issue. The fix isn't another button to train people on; it's making Jira's own Create screen produce the right shape, every time.

How it works

1

Build a template

Define the default fields, sub-tasks and hierarchy for an issue type once — per project or per issue type — with full field pre-fill, including custom fields.

2

Create, natively

Your team creates issues exactly as they always have — right on Jira's native Create screen — and the template pre-fills summary, fields and structure in one click.

3

Scaffold whole trees

Need an epic with its stories and sub-tasks? One template scaffolds the full tree with fields pre-filled at every level. No shadow projects, no admin rights required.

A Datum app

the promise

Like every Datum app, Prefab is Forge-native and runs inside your own Jira site — free for up to 10 users, with a single honest paid plan after. No separate sign-up, no data leaving your tenant. Why Datum →

Screenshots

Click any shot to view it full size.

FAQ

Does it change how we create issues?

No — templates live on the native Create screen. There's no separate button or screen to retrain your team on, which is why adoption is a non-issue.

Can it build hierarchies?

Yes. Templates scaffold epic → story → sub-task trees in one click, with fields pre-filled at every level — the pattern Scrum teams rebuild by hand today.

What's on the free tier?

Unlimited templates with hierarchy and full field pre-fill, default templates per issue type/project, and import/export. Standard adds variables & forms, automation-triggered templates, and a bulk JSON importer for migrating templates from another app — free up to 10 users.

Works well with

Cadence Auto-create Jira issues on a schedule — recurring tasks, ceremonies and maintenance, from full templates. Tally Roll sub-task and child-issue progress up to the epic — status, story points and % complete, right on the parent. Trailkeeper The field-change history and audit trail Jira's native activity view leaves out — who, what, when, from → to.

Explore all Datum apps →

Guides

Best Jira issue template apps (2026) A side-by-side comparison of the best Jira issue template apps in 2026 — what each does, how they're priced, and which fits a small team versus a large rollout. A Deviniti alternative for Jira templates A Deviniti Issue Templates alternative for Jira Cloud — the Forge-native options compared on setup, pricing and hierarchy, plus where Deviniti still wins. How to create a bug report template in Jira Bug reports with missing steps or environment slow everyone down. Here's a reusable Jira bug template that pre-fills the fields every report needs. How to create a sub-task template in Jira Jira has no built-in sub-task template — you re-add the same sub-tasks by hand. Here's how to save a reusable one and apply it in one click. Jira Automation vs issue templates — which should create your issues? Both Jira Automation and issue templates can create issues, but they solve different problems. Here's when to use each — and when to use both together. Jira issue types vs issue templates — what's the difference? Issue types and templates sound similar but do different jobs. Here's what each is, why a Bug type isn't a Bug template, and how they work together. How to bulk-create subtasks in Jira (without adding them one by one) Jira adds subtasks one at a time. Here's how to bulk-create a whole set at once — by CSV, automation, or a reusable template that fills the fields too. How to pre-fill fields on the Jira Create screen Retyping priority, labels and fields on every new Jira issue is slow. Here's how to pre-fill the Create screen so issues start correct and consistent. How to create a Jira epic with stories and sub-tasks in one step Adding each story and sub-task to an epic by hand is slow. Here's why Jira can't build the hierarchy at once — and how to spin up the tree from a template. How to create issue templates in Jira Jira has no native issue-template feature. Here are the ways to pre-fill and standardise Jira issues — from field defaults to full hierarchy templates. How to duplicate a Jira issue Jira's Clone copies an issue once but skips fields and can't be reused. Here's where it falls short — and how to make a repeatable issue structure instead.

Get Prefab

Free for up to 10 users, with one honest paid plan after. See pricing →

Get it on the Atlassian Marketplace →