Overview

What can you do with templates?

With this app you can:

• Create single work items from templates: Create work items with pre-filled fields in a few clicks instead of starting from an empty form.

• Create full structures in one go: Create complete hierarchies, for example, an epic with its stories and subtasks, so recurring work always follows the same shape.

• Apply templates to existing work items: Standardise messy or ad-hoc work by updating summaries, descriptions and fields without losing history or links.

• Schedule recurring work: create monthly, quarterly, or annual tasks automatically, with the right fields, assignees, and dates already set.

• Create related work items with smart cloning: Create a new related work item that pre-fills only the essential fields from the current one and links them automatically, so nothing has to be retyped or tracked by hand.

• Use dynamic content instead of static text: prefill fields, descriptions and checklists with variables and date offsets, so each created work item reflects its context without manual edits.

The goal is simple: less manual setup, fewer mistakes, and more consistent work.

Who is this app for?

Work Templates is designed for:

• Admins and process owners who want a controlled catalogue of templates, with clear rules about where they can be used and by whom.

• Team leads and coordinators who run the same type of work repeatedly and need to create reliable structures and fields without having to hand-build them each time.

• Power users who want to create the right work in one go, with the correct fields and links already in place, instead of copying details across by hand.

• Teams running large, repetitive operations such as support, operations, finance, HR or compliance, where small mistakes and manual setup add up across many similar tasks every day.

Key concepts

These concepts appear throughout the documentation:

• Template: a predefined blueprint for a single work item, where a template owner can define values with which fields will be set when the work item is created

• Template repository: the shared library where templates and structure templates are stored, managed and accessed by users.

• Template context: the scope where a template is available, for example, in specific projects, work types or request types.

• Structure template: a template that creates several linked work items in one go, for example, an initiative with epics, stories and subtasks.

• Create and link: an action from the work item view that creates a new work item from a chosen template, copies only the selected fields from the current work item and links the two with a chosen link type.

• Scheduler: a configuration that creates work from templates on a repeating schedule (e.g. monthly checks, quarterly reviews or annual tasks).

• Variables and date offsets: Dynamic values you can place inside templates so that fields are calculated when work is created, for example, reporter name, project key or a due date such as “today plus five days”.

Where teams use work templates

Teams adopt our app as a solution wherever the same work keeps coming back, and small mistakes are costly. For example

• Service and operations work: recurring maintenance, incident reviews, capacity checks, on-call handovers – all created on a schedule with the right fields, owners and dates already set. 

• HR workflows: onboarding and offboarding, role or location changes, equipment handover, sick leave and other standard requests, so every person goes through the same clear set of steps. 

• Finance and billing cycles: monthly invoices, subscription renewals, purchase approvals and regular financial reviews, using templates to keep data fields and reporting structures consistent across periods and projects. 

• Governance, risk, compliance and qa: recurring audits, control checks, risk reviews, test cycles and evidence collection, with structured task bundles that ensure nothing on the checklist is quietly forgotten. 

• Project and product delivery: new project kick-offs, release preparation, feature delivery epics and standard implementation packages, so multi-project work follows the same pattern every time instead of being rebuilt from scratch. 

In all of these areas, our app gives you a single, agreed way of doing recurring work, while still letting teams adapt details where it makes sense.