Create Issue using Template
Learn how to turn any Jira issue into a reusable template and configure it for automated or manual use across your Jira projects.
🧩 What is an Issue Template?
An issue template in Templify is a regular Jira issue that has been marked as a template using the Templify app. Once marked, it can be reused to generate new issues, prefill create forms, or serve as a foundation for hierarchical issue structures.
Templify stores additional metadata and configuration behind the scenes to extend the behavior of this issue – but it remains fully editable like any other Jira issue.
🛠 Where to Manage Templates?
Templify adds a dedicated section called Issue Templates on the Jira issue view. From this panel, you can:
Mark or unmark the issue as a template
Configure template properties (dynamic values, visibility)
Access features, such as “Create from template”
This seamless integration ensures templates are managed exactly where issues live – within the context of your existing Jira instance.
🔄 What Happens After Marking an Issue as a Template?
Once an issue is set as a template, it becomes available in multiple places:
✅ “Create from Template” action: instantly generate a new Jira issue based on this template (with or without hierarchy, links).
✅ Issue Template Picker: select it from a dropdown in the native Jira Create Issue form to prefill fields and structure.
✅ Default values per project/issue type: configure this template to automatically prefill new issues for a specific context.
Templify ensures that templates can be reused consistently, no matter where your users work inside Jira.
🧪 Interactive Demo
Below is a step-by-step interactive walkthrough showing how to:
Open a Jira issue
Mark it as a template
Configure its properties (e.g., labels, type, hierarchy settings)
Preview how the template works in real-time
This demo will help you get started quickly and explore the full potential of issue templates.
Tip: Templates can be updated at any time. Changes apply immediately when the template is used next.
📌 Best Practices
Create templates from well-structured, production-ready issues
Use clear summaries and dynamic variables in fields to increase reusability
Avoid duplicating similar templates – instead, use dynamic expressions to adapt content
Last updated