Create subtasks automatically in Jira

Option 1: Jira Automation

1. Create a project automation rule.
2. Choose a trigger such as work item created or status changed.
3. Add one Create sub-task action for each required task.
4. Test the rule in a non-production project and inspect its audit log.

This works well for a fixed checklist tied to a predictable event. It becomes harder to manage when people need to choose among processes, enter values at run time, preview the tree, or understand a partial failure across several create actions.

Option 2: a reusable subtask template

A template is a better fit when a user should decide when to apply a process. With TreeGuard, a project administrator defines the subtask summaries and run-time values once. A user then opens an issue, selects Add subtasks from template, reviews the result, and starts the run.

TreeGuard checks create metadata and required fields before the first mutation. It creates each issue in order, reads it back, verifies the configured values and parent link, and attempts reverse cleanup if a later step fails.

Example: release checklist

Cut release branch for {{version}} | due=+1 | assign=me
Run regression suite for {{version}} | due=+2
Update release notes for {{version}} | due=+3
Deploy {{version}} to production | due=+4

The person running the template supplies the version once. Due dates are calculated from the run date, and assign=me assigns that task to the runner.