Changelog — Prefab
Version numbers here are Datum release numbers. The version Jira or Confluence shows for the app is assigned by Atlassian and may differ.
v2.2.1 · 2026-11-16
- Clearer German, French and Spanish wording after a translation review, using Atlassian's own Jira and Confluence terms.
v2.2.0 · 2026-11-16
- Prefab now speaks German, French and Spanish — it follows each person's Jira language.
- The Rovo template agent now only reports templates it actually created.
v2.1.1 · 2026-11-14
- "Make recurring" now points to Encore, the new name of Datum's recurring-issues app (formerly Cadence). The export format is unchanged.
v2.1.0 · 2026-11-14
- Easier Create-screen pre-fill setup: a project's first template starts with pre-fill switched on, templates without a default get a one-click "Make default", and the project page shows a banner with "Turn on pre-fill" when it's off.
- The global Prefab page lists every project that has templates, shows whether pre-fill is on, off or waiting for Jira, and lets project admins turn it on in one click.
v2.0.1 · 2026-11-13
- Jira admins are now treated as project admins everywhere Prefab checks for one, so they can manage any project's templates.
v2.0.0 · 2026-11-13
- Needs admin approval when you update: Prefab asks for two new permissions, one to read service-desk request types (for portal pre-fill) and one to rank issues (to keep template order).
- Template permissions (Standard): choose who can see, apply or edit each template, or a whole folder of templates, by Jira group or project role. Admins can never be locked out.
- Checklists: add a checklist to any template and its sub-issues; the items appear in the description as Jira checkboxes. Free.
- Customer-portal pre-fill (Preview): in a service project, pick a template per request type and the portal request form starts pre-filled. Anonymous portals and the embedded widget aren't supported yet. Free.
- Transition-screen pre-fill (Preview): pick a template per target status and Prefab fills the empty fields on the transition screen. Values already on the issue are never overwritten. Free.
- Apply anywhere: create from a template in any project you can see, or add the template's sub-issues under the issue you're on. Free.
- REST API (Standard): apply a template from scripts or CI with one authenticated request, pass your own job id, and check whether the job is queued, running, done, partial or failed. Issues it creates can be found with JQL.
- Make recurring with Encore (formerly Cadence): each template can be exported in the format Datum's Encore app imports, with the steps to schedule it. Prefab itself doesn't schedule issues.
- Big epics keep their order: stories and sub-tasks are ranked in the order the template lists them. Free.
- Template health check: Prefab lists fields, options, users and issue types a template uses that no longer exist in the project, and can remove the broken values in one click. Free.
- Import from Deviniti's Issue Templates: turn the issues in a templates project into Prefab templates, up to 500 issues per import. Free.
- Apply on transition (Standard): an automation rule can create a template's issues when an issue moves into a status you pick, at most once per issue.
v1.1.2 · 2026-11-12
- The settings page now says plainly which Create screens the pre-fill applies to.
v1.1.1 · 2026-11-12
- Fixed: the Rovo action for generating a template crashed, and generated sub-tasks weren't created.
v1.1.0 · 2026-11-12
- Fixed: pre-filling Jira's own Create screen from a template didn't work. It now fills the template's fields when you pick the project and issue type the template is set up for.
- Deleted projects no longer stop pre-fill from syncing for the remaining projects.
v1.0.10 · 2026-11-11
- Maintenance release: updated Atlassian UI libraries. No visible changes.
v1.0.8 · 2026-10-25
- More reliable saving when several people edit templates at the same time, and no size ceiling on large template libraries.
v1.0.7 · 2026-10-25
- Deleting a template now also deletes its saved version history.
v1.0.6 · 2026-10-25
- Security fix: only admins can create, change or delete templates through Prefab's settings.
v1.0.5 · 2026-10-25
- Paid features used by automation rules now check the licence when the rule runs, not only when it was set up.
v1.0.4 · 2026-10-24
- Automation runs that only partly succeed now say which issues failed, and progress totals are correct.
- Template version history is included in Atlassian's personal-data reporting and erasure.
- Security: the issue Prefab acts on is read from Jira's own context, not from the browser.
v1.0.2 · 2026-10-09
- Interface brought in line with Atlassian's design system: clearer labels, empty states and dialogs.
- Fixed: hierarchy templates could build an invalid tree. Prefab now offers sub-tasks at the right level and checks the tree before saving.
- Fixed: the issue-type list could come up empty for some projects.
- Template version history is now a Standard feature.
- Weekly personal-data reporting to Atlassian, as Marketplace apps are required to do.
v1.0.1 · 2026-09-06
- Marketplace licensing switched on, so the Standard plan can be bought and checked in the app.
v1.0.0 · 2026-09-05
- First release: templates for epics, stories and sub-tasks with every field pre-set, applied from the issue view or Jira's Create screen.
- Global templates shared across projects, rich-text descriptions, people pickers, import and export.
- Large hierarchies are created in the background with progress, and only the failed part is retried after a partial failure.
- Standard plan: template variables with an apply-time form, automation-triggered templates, version history, an audit log and an importer from other template apps.
- Generate a template from a plain-language description with Rovo.