Changelog
This page lists notable changes shipped with each release of Templify. The most recent update is shown first.
The app is updated through the Atlassian Marketplace. Your Jira Cloud site receives new versions automatically — no manual upgrade is required.
Release: 2026-05-30
Ready-to-go Templates from the gallery
Start from a built-in catalog of curated, ready-made templates instead of building each one from a blank issue. Open the gallery, point a template at one of your projects, and Templify creates it for you as a fully working, reusable template.
- Create from gallery — a new action on the Issue Templates page opens a browsable catalog of ready-made packs.
- Any project, full structure — create into any of your projects, with the template's complete issue hierarchy (parent, child issues, and subtasks), not just a single issue.
- Saved as a reusable template — creating from the gallery builds the issues and registers the result in your template list, ready to use, edit, and configure like any template you built yourself.
Release: 2026-05-21
Import / Export templates
Move templates between Jira sites, back them up, or share a curated library with another team — all from the global template list.
- Export selected templates — pick any subset of templates from the global list and download them as a single file.
- Import in two modes — Add as new keeps your existing templates and creates fresh copies, Replace existing updates templates that match by name.
- Preserves the full template definition — fields, default values, dynamic fields, dynamic text fields, subtasks, child issues, and links all round-trip through export and import.
- Cross-site friendly — the importer remaps project- and issue-type-specific data so a template exported from one Jira site can be imported into another.
Release: 2026-03-08
Dynamic text fields propagate through the whole hierarchy
Values you type into a dynamic text field when creating from a template are now reused across every issue in the structure — parent, children, and grandchildren — so a single answer fills the same placeholder everywhere it appears.
- Save once, apply everywhere — entering a value on the parent automatically replaces the same placeholder in subtasks, child issues, and child-of-child issues.
- Child-of-template context on the issue panel — when you open an issue created as a child of a template run, the Templify panel now recognises the context and offers the right follow-up actions.
- Consistent across Create-from-template and Apply-template flows — both entry points respect the propagated values.
Release: 2026-01-02
Backend permission checks
Permission validation now runs on the backend for every template action, closing gaps where the UI was the only gatekeeper. End-users see no change in normal flows, but unauthorized actions are rejected even if the UI is bypassed.
- Server-side enforcement — create, update, delete, and apply actions are validated against the user's project and global permissions before any change is persisted.
- Clearer error messages — when a permission check fails the dialog explains why instead of just failing silently.
Release: 2025-12-29
Global vs Project template availability
Each template can now be marked as Global (available across every project) or scoped to specific projects, giving admins fine-grained control over which teams see which templates.
- Per-template availability setting — choose Global or pick one or more projects directly from the template configuration.
- Filters propagate everywhere — the Create-from-template picker, the Issue Template field, and the Apply-template dialog all respect the configured availability.
- Faster pickers — restricting templates to relevant projects keeps the picker short and on-topic.
Release: 2025-12-14
Apply template — Jira automation action
A new Jira automation action that applies a Templify template to an issue from any automation rule. Use it to auto-fill issues created by intake forms, transitions, or scheduled rules.
- No-code integration — drop the Apply Templify template action into any rule and pick the template to apply.
- Works with subtasks, child issues, and links — the full template structure is created when the rule fires, just like a manual Create from template.
- Pairs with existing rules — combine with Jira's smart values to apply different templates based on issue type, project, or labels.
Use the Jira automation action
Audit logs + license validation
- Audit logs — every template create, update, delete, and apply action is now recorded in a per-instance audit log. Admins can review who changed what, and when, from the Administration area.
- License validation — the app now validates the Atlassian Marketplace license on each call and shows a clear message if the license is missing or expired, instead of failing with a generic error.
Release: 2025-09-23
Schema migration screen
Apps that need a one-time schema migration after upgrade now show a dedicated progress screen instead of silently retrying in the background. End-users and admins can see exactly what is being migrated and when it is safe to use the affected features.
- Visible migration status on every screen that depends on it.
- Automatic retry — the migration runs on app install and on demand, so reinstalling the app is no longer required to recover.
Release: 2025-08-26
Skip the structure step when there is nothing to create
Creating from a template that contains only an epic — with no children — no longer forces you through an empty structure preview. The dialog skips straight to the result.
- Cleaner flow for simple templates — no extra confirmation step when there are no subtasks or child issues to review.
- Reused login state in Playwright — internal test improvement; not user-visible but reduces flaky deploys.