Skip to main content

Changelog

This page lists notable changes shipped with each release of Templify. The most recent update is shown first.

info

The app is updated through the Atlassian Marketplace. Your Jira Cloud site receives new versions automatically — no manual upgrade is required.

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.

Import / Export templates

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.

Use dynamic text fields

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.

Permissions

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.

Template availability

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.

Audit logs

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.

Release: 2025-08-25​

Pre-fill dynamic text field dialog from the Create form​

Values already entered in the Jira create form are now copied into the dynamic text field dialog when it opens, so you don't have to retype Summary, Reporter, or anything else that's already on the screen.

  • Less duplicate typing — Summary and other shared fields appear pre-filled.
  • Edits still flow back — adjusting a value in the dynamic text field dialog updates the create form when you confirm.

Use dynamic text fields

Release: 2025-06-29​

Issue keys visible on the structure preview​

After creating issues from a template, the structure result step now shows the real issue key (e.g. PROJ-123) for every issue that was created, with a click-through to open it in Jira.

  • One-click access to each new issue from the success screen.
  • Easier verification of what was actually created when running large templates.

Release: 2025-06-26​

Production stabilisation + UI polish​

A round of fixes shipped with the first wave of customer feedback.

  • Hidden Refresh button — removed an internal-only Refresh button that occasionally caused confusion in the global template list.
  • Many small UI fixes — issue type picker, template picker, get-started page links, footer logo, and column sizing on the global page.

Release: 2025-06-16​

Apply template — handle children, links, and subtasks​

Applying a template to an existing issue now mirrors the Create from template dialog: the full structure (subtasks, child issues, and issue links) is recreated against the target issue in one pass.

  • Subtasks, child issues, and links recreated when applying a template to an existing issue.
  • Single load step — all run-time issues are fetched in one query, so the dialog opens noticeably faster on large templates.
  • Hierarchy-aware — only templates at the same hierarchy level as the target issue are offered, so you can't accidentally apply an epic-shaped template to a story.

Apply a template to an existing issue

Release: 2025-06-15​

Sync / Async issue structure creator​

A rewritten engine for creating multi-level issue structures from a template, with a dedicated result step so you can see what was created before closing the dialog.

  • Bulk create service — issues are created in batches, with links and child issues queued in the background to avoid Forge function timeouts.
  • Structure result step — review the full created tree (epic → stories → subtasks) before dismissing the dialog.
  • Subtle animations on the structure preview so it's easier to follow which issue is being created.

Create an issue hierarchy

Release: 2025-06-04​

Dynamic user fields​

Three new dynamic field types for assigning people automatically when creating from a template.

  • Dynamic user field — resolves to the current user, or any user picked at create time.
  • Dynamic assignee — defaults the assignee based on rules configured in the template.
  • Dynamic multi-user field — pre-fills multi-user fields (watchers, approvers, reviewers) from a template.

Use dynamic fields

Release: 2025-05-28​

Usage history​

The Templify panel on the issue view now shows the usage history for the current template — every time it was applied, by whom, and against which issues.

  • Per-template history table on the issue panel.
  • Full issue structure for each run, so you can see exactly what was created.
  • Searchable from the global template list — see how often each template is actually used.

View usage history

Release: 2025-05-23​

Create child issues from an epic template + copy issue links​

Templates for epics now create their full child structure on apply, and issue links defined in the template are copied across into the new issues.

  • Create child issues for an epic — template runs from an epic template create the configured stories/tasks underneath.
  • Copy issue links — link types (blocks, relates to, duplicates, etc.) defined on the template are recreated on the new issues.
  • Auto-save as template in global repository — when the global repository is enabled, saving an issue as a template automatically registers it in the global list.
  • Select parent when creating from a subtask template — the dialog asks for the parent issue when the template is a subtask.

Create an issue using a template

Release: 2025-05-01​

Templify — initial release​

The first public release of Templify. Save any Jira issue as a template, then create new issues — or apply the template to existing issues — with the full field set, subtasks, dynamic content, and default values pre-filled.

  • Issue Template custom field — attach a template to any project / issue type combination.
  • Create from template — open the create dialog with every field, attachment placeholder, and subtask pre-filled.
  • Apply template to existing issue — fill an existing issue with the template values in one click.
  • Set default template — auto-fill the create form whenever a project / issue type combination is opened.
  • Dynamic fields — resolve to now, today + N days, or the current user at create time.
  • Dynamic text fields — placeholder-style variables in Summary, Description, and other text fields, resolved from a dialog at create time.
  • Global template repository — share templates across every project on the instance.
  • Configurable per project — permissions, default template, and which dialogs the app appears in.
  • Runs on Atlassian Forge — no external servers, no data egress.

Quick guide