Build a Jira issue template with subtasks

Choose the smallest useful tree

Use a standard issue plus subtasks when one owner coordinates a short checklist. Use an Epic plus child issues and their subtasks when the process has independently owned work streams. Avoid adding levels merely to make the template look comprehensive.

Preserve Jira's hierarchy rules

A standard Jira issue can contain subtasks. An Epic can contain standard child issues, which can each contain subtasks. The available issue types vary by project, so a reusable template should validate the live project's create metadata rather than assuming names such as Story, Task, or Sub-task always exist.

Create parent first, then verify each link

1. Validate every issue type and required field.
2. Create and verify the root before creating its children.
3. Create each child only after its parent has been confirmed.
4. Read each issue back and compare its configured fields.
5. On failure, delete created descendants before their parents.

TreeGuard follows this order and stores a private execution receipt. Jira has no transaction for multi-issue creation, so cleanup is best effort and any unresolved result remains visible.