
Organize template sets in folders
Version 28.1.0 lets you manage a template set's folders from its header: tick a folder to save, undo in one click, and see folder changes in the history.
How-tos, release notes and processes from the team that builds AppsDelivered Templates, Comments and Feeds.

Connect AppsDelivered Templates to a Slack channel with an incoming webhook, so your team sees when recurring work is created.
Riley Venable · 2 min readNo posts on this topic yet.

Version 28.1.0 lets you manage a template set's folders from its header: tick a folder to save, undo in one click, and see folder changes in the history.

Two ways to bring templates and template sets from Jira Data Center to Cloud: with the Jira Cloud Migration Assistant, or by export and import.

The calendar view shows every scheduled template set by month, week, day or as an agenda, so you can spot gaps and clashes before they happen.

Version 27.5.0 adds protected fields. When it's on, applying a template in the Create dialog keeps what someone already typed in a field. It's off by default.

The History page logs every change to templates and template sets: who made it, what changed, and the value before. Useful for audits and for debugging.

Limit templates to the people and teams they're meant for. How template restrictions and comment template groups keep each list short and safe.

Give every bug the same three steps: reproduce, triage, verify. A bug template fills in the report, and a template set adds the steps with owners.

Put your weekly review on a schedule: the review work item and its agenda arrive every Friday morning in your time zone, ready to fill in.

Since version 27.0.0, you can pick an existing epic or feature as the parent when you apply a template set, so the set adds only the child work items.

Most of PI planning happens before the event. Build the prep work once as a template set, and start each increment with the same checklist.

Turn incident and maintenance notices from the services your team relies on into Jira work items, so someone owns the 'is it down?' question.

Write a follow-up or reminder on a work item and pick when it posts. How scheduled comments work, who can see them, and when to use them.

Use a workflow post function to apply a template set at the right moment, such as creating onboarding work when an HR request is approved.

Turn your release steps into a template set with a checklist, then apply it for each version with the version number filled in.

A vulnerability workflow in three steps: a feed creates the advisory work item, a reviewer triages it, and a template set rolls out the patch.

Keep agent discussion next to the request without the customer seeing it. How internal threads and replies at any depth keep busy requests readable.

Build onboarding once: accounts, equipment and first-week tasks, each with an owner. Then apply it for every new person with their name filled in.

Comment templates your agents will actually use: a short list, variables for the details, and groups that show each template only where it fits.

Variables let one template set serve every run: today's date, the space, the reporter, a new hire's name. Here are the ones we use most.

Follow your vendors' official advisory feeds in Jira. Each new advisory becomes a work item with a reviewer, so nothing waits in someone's inbox.

Three ways to create recurring work in Jira Cloud: clone by hand, a scheduled Jira Automation rule, or a template set on a schedule. When each one fits.

Set up a monthly access review once: one work item for the review, a subtask per system, an owner for each, created on the same day every month.
Guides from 2024. Most use our apps' old names, such as Smart Issue Templates, and Jira's old word "issue" for what is now a work item.