Skip to main content

FAQ

Find answers to the most common questions about Templify. Click any question to expand the answer.

Templates​

What types of Jira issues can be used as templates?

Any Jira issue can be marked as a template — Tasks, Stories, Bugs, Epics, Sub-tasks, and custom issue types. Simply open the issue and use the Templify panel to mark it as a template.

The issue itself remains a regular Jira issue and can still be used in your workflows. Marking it as a template simply makes it available for reuse.

Learn how to create templates

Can a template include child issues (hierarchies)?

Yes. Templify supports issue hierarchies — when you mark a parent issue as a template, its child issues are included. Creating from that template generates the entire tree (e.g., Epic → Stories → Sub-tasks) in one click.

Child issues can even belong to different projects or boards. Any dynamic fields or dynamic text fields configured on child issues are automatically resolved during creation.

Create Issue Hierarchies

Are a template's attachments copied to new issues?

Yes. Files attached to a template are copied to every issue created from it: from the Create from Template dialog, from Jira's Create form (picked in the Issue Template field or set as the default), and by the Create issue from template Automation action. In a hierarchy, each sub-task and child issue gets the files of its own template issue. Applying a template to an existing issue copies its files too, without adding a file the issue already holds.

An image pasted into the template's description arrives as an attachment, and the description keeps its text. Files larger than 100 MB are not copied. The files appear on the new issue shortly after it is created.

Where should I store my templates?

You have two options:

  • In any project — templates stored in a specific project are available within that project (and can be shared via Template Availability settings)
  • In the Global Repository — a designated project that serves as a centralized template library, making templates available across your entire organization

For most teams, using the Global Repository is recommended as it keeps templates organized and accessible.

Set up the Global Repository

Can I control which projects see which templates?

Yes. Use Template Availability to restrict templates to specific projects. This ensures teams only see templates relevant to their workflows.

By default, templates in the Global Repository are available to all projects unless restricted.

Configure Template Availability

Create Issue Form​

Why don't I see the Issue Template Field in the Create Issue form?

The Issue Template Field is only available on the Global Create Issue screen — the dialog opened via the top navigation "Create" button or the C keyboard shortcut.

If you're creating issues from a board, backlog, or inline creation, the template field won't appear.

For Company-Managed projects: Templify adds the field to the Create screen when you add the project on the Issue Template field tab, or when you save a default template for it.

For Team-Managed projects: You need to manually add the Issue Template field to your project. Go to Project Settings → Fields and add it.

Configure the Issue Template Field

What is the difference between the Template Field and Default Values?

These are two separate features for prefilling the Create Issue form:

  • Issue Template Field — adds a dropdown to the form where users manually select a template. The form is then populated with that template's values.
  • Default Values — automatically prefills the form based on the project and issue type combination, without any user interaction.

You can use both features together: Default Values provide a baseline, and users can override by selecting a different template from the dropdown.

Template Field · Default Values

Dynamic Fields​

What are dynamic fields and how do they work?

Dynamic fields use expressions that are evaluated at the time of issue creation, rather than storing static values. For example:

  • today + 7d → sets the due date to 7 days from now
  • Board name (e.g., SP board) → assigns the active sprint of the selected board
  • Creator → sets the field to whoever is creating the issue

This means each issue created from the template gets context-relevant values automatically.

Dynamic Fields reference

Can I use dynamic placeholders in the Summary or Description?

Yes. Dynamic Text Fields let you add placeholders to text fields like Summary and Description. These placeholders can:

  • Prompt the user for input: {Summary:text}
  • Offer a dropdown selection: {Environment:select(Dev,Staging,Prod)}
  • Insert automatic values: {Reporter:Creator}

Dynamic Text Fields reference

Permissions and Security​

Who can create and manage templates?

Templify uses a role-based permission model:

  • Use Templates — available to all users by default; allows creating issues from templates and selecting templates in the Create Issue form
  • Manage Templates — restricted to Jira Administrators and Project Administrators by default; allows marking issues as templates, configuring availability, and setting default values

Permissions can be customized per your organization's needs.

Manage Permissions

Automation​

Can I use templates with Jira Automation?

Yes. Templify provides two custom actions for Jira Automation:

  • Create issue from template — generates a new issue based on a template when an automation rule triggers
  • Apply issue template — applies a template's field values and attachments to an existing issue, and can add the template's sub-tasks, child issues and links to it

This allows you to automate template-based workflows — for example, automatically creating a set of onboarding tasks when a new employee issue is created.

Jira Automation Actions

Troubleshooting​

Template field values are not appearing on the created issue

Check the following:

  1. Field availability — ensure the target field exists in the destination project's screen scheme
  2. Field context — verify the field context includes the target project and issue type
  3. Permissions — confirm the user has permission to set the field value
  4. Dynamic field syntax — if using dynamic expressions, verify the syntax is correct

If the issue persists, check the Audit Logs for error details.

Default Values are not prefilling the Create Issue form

Default Values only work on the Global Create Issue screen. Verify that:

  1. You're using the global "Create" button (top navigation) or the C shortcut
  2. A default template is configured for the selected project and issue type combination
  3. The user has the "Use Templates" permission

Configure Default Values

Sub-tasks, child issues or attachments are missing after Jira's Create form

Templify adds them right after the issue is created, so give it a moment and refresh the issue. If they still don't appear, check that:

  1. The Issue Template field is on the project's Create screen — Templify adds them through this field. Saving a default template puts the field there, and the Set default dialog says where it could not
  2. The template is available in the project — see Template Availability
  3. The person creating the issue can see the template issue — Templify does not apply a template whose issue they cannot browse

Configure the Issue Template Field

Still Need Help?​

If your question isn't answered here: