Key Concepts
This page explains the fundamental terms and concepts you'll encounter when working with Templify. Understanding these will help you get the most out of the app and navigate the documentation with confidence.
Issue Template
An Issue Template is a regular Jira issue that has been marked as reusable in Templify. It stores predefined field values, configuration, and optionally child issues — serving as a blueprint for creating new issues or entire structures.
Templates can be stored in any project or in a centralized Global Repository.
Any Jira issue can become a template — simply mark it using the Templify panel on the issue view. Learn how in Create Issue using Template.
Global Repository
The Global Repository is a designated Jira project that serves as a centralized storage location for templates. When configured, templates stored here are available across all projects (subject to Template Availability rules).
This allows teams to share and reuse templates organization-wide without duplicating them per project.
Learn more about Global Repository setup
Template Availability
Template Availability controls which projects can see and use each template. Administrators can restrict templates to specific projects, ensuring that teams only see templates relevant to their workflows.
Configure Template Availability
Issue Template Field
The Issue Template Field is a custom single-select field provided by Templify. When added to the Create Issue form, it displays a dropdown list of available templates. Selecting a template automatically populates the form with predefined values.
This field is only available on the Global Create Issue screen (opened via the top-nav "Create" button or the C keyboard shortcut).
Set up the Issue Template Field
Default Values
Default Values (also called Default Templates) allow you to assign a template to a specific project and issue type combination. When a user opens the Global Create Issue form for that combination, Templify automatically prefills the form in the background — no user interaction needed.
This is ideal for enforcing consistent field values across teams without requiring users to manually select a template.
Issue Hierarchy
An Issue Hierarchy (or Issue Structure) is a template that includes parent-child relationships. When applied, Templify creates the entire tree of issues in one click — for example, an Epic with its Stories and Sub-tasks.
Hierarchies can span across projects and boards, making them ideal for project kickoffs, onboarding flows, or recurring processes.
Dynamic Fields
Dynamic Fields are template fields that use expressions evaluated at the time of issue creation. Instead of static values, they calculate context-relevant results.
Examples of dynamic expressions:
| Expression | Result |
|---|---|
today + 7d | Due date set to 7 days from creation |
currentSprint | Assigns the issue to the active sprint |
currentUser | Sets the field to the user creating the issue |
Dynamic Text Fields
Dynamic Text Fields extend the dynamic concept to text-based fields like Summary and Description. They support placeholders that are replaced with real-time values or user-provided input when a template is applied.
Examples:
| Placeholder | Purpose |
|---|---|
{Summary:text} | Prompts the user for a text input |
{Environment:select(Dev,Staging,Prod)} | Displays a dropdown for selection |
{Reporter:currentUser} | Inserts the current user's name |
Learn about Dynamic Text Fields
Apply Template
Applying a template means copying the template's field values onto an existing issue. Unlike creating from a template (which generates a new issue), applying overwrites specific fields on a target issue.
When you apply a template to an existing issue, matching field values will be overwritten. This action cannot be undone.
Apply Template to Existing Issue
Jira Automation Actions
Templify provides two custom actions for Jira Automation rules:
- Create from Template — generates a new issue based on a template, triggered by automation events
- Apply Template — applies a template's values to an existing issue within an automation flow
These actions let you automate template-based workflows without manual intervention.
Global Create Issue Screen
The Global Create Issue screen is the main issue creation dialog in Jira, accessed via the top navigation "Create" button or the C keyboard shortcut. Templify integrates with this screen to support:
- Template selection via the Issue Template Field
- Automatic prefill via Default Values
The Global Create Issue screen is different from creating issues directly on a board or backlog. Templify's form-level features (template picker, default values) only work on the Global Create screen.