---
description: >-
  Automatically generate full issue hierarchies — including sub-tasks, Epics,
  and linked issues — from a single reusable template.
---

# Create Issue Hierarchy

## Create Issue Hierarchy

Templify allows you to automate the creation of entire **issue structures** — including **Epics**, **Stories**, **Tasks**, **Sub-tasks**, and **linked issues** — from a single, reusable template.

Instead of manually building each issue and relationship one by one, you can define a complete hierarchy once and use it repeatedly across teams and projects.

***

### 🧩 What It Does

When a user creates an issue from a template that contains children or links, Templify will:

* Automatically create all child issues (e.g. Sub-tasks under a Task, Stories under an Epic)
* Preserve hierarchy relationships — parent/child, Epic links, etc.
* Apply issue links (e.g. _blocks_, _relates to_) based on the original template structure

This behavior is consistent and reliable across all supported projects and issue types.

***

### ⚙️ How to Create Hierarchies

There are two simple ways to trigger hierarchy creation:

1. **Use the "Create from Template" action**\
   → Available in the _Issue Template panel_ on any issue marked as a template
2. **Select a template in the Jira Create Issue form**\
   → When the issue is created, Templify will automatically generate the full hierarchy in the background

> 🔁 This process is fully automated — there is no need to manually configure subtasks, add stories to epics, or apply links afterward.

***

### ✅ Why It Matters

Templify’s hierarchy support eliminates the most repetitive and error-prone parts of project setup. You get:

* ⚡ Faster onboarding and epic creation
* 🔁 Consistent structure across teams and processes
* 🔒 Reduced risk of missing critical dependencies or steps
* 📈 Scalability — use the same patterns in multiple projects, versions, or departments

Managers and project leads can ensure every initiative starts with the right setup — without relying on tribal knowledge or extra training.

***

### 🧪 Interactive Demo

The interactive demo below shows how to create issue structures in two ways.

#### Demo 1: Use Create Issue form

* Select an issue template from the native **Create Issue** form
* Configure the template to include **child issues** (e.g. Sub-tasks, Stories)
* Set up **linked issues** to mirror real-world dependencies and flows

{% @arcade/embed flowId="P71zD09vsUTfiRBRqPX0" url="https://app.arcade.software/share/P71zD09vsUTfiRBRqPX0" fullWidth="true" %}

#### Demo 2: Configuring Your Template Structure

* Open the issue marked as a template and click **Create Issue**
* Choose your target project and desired issue type
* Use the hierarchy preview to toggle which child issues get created

{% @arcade/embed flowId="XMDxzpyvOi61F7ccCcLI" url="https://app.arcade.software/share/XMDxzpyvOi61F7ccCcLI" fullWidth="true" %}

***

### 📌 Best Practices

* Create issue hierarchies **directly from the Issue Template panel** if you want the full structure to be generated **synchronously**, with immediate visual results in Jira.
* If a template contains a **large or complex structure** and you want to restrict its usage, you can mark it as **"not visible" in the Issue Template field**.\
  → This allows to use the template manually while hiding it from everyday users in the Create Issue form.
* Use this option to limit access to heavy templates while keeping them reusable in controlled workflows.
