Documentation
Some teams do the same shaped work over and over. A client is onboarded, a release goes out, an incident gets a postmortem, a new starter needs accounts and a buddy. Every time, somebody rebuilds the same epic, the same stories, the same sub-tasks by hand.
Open any epic, choose Save as issue tree template, and the app captures it: child items, sub-tasks, their field values and the links between them. That is the entire setup. No shadow project, no screens to configure, and capture only ever reads.
Then create the whole structure in any project in one click, with variables filled in as you go.
Before anything is created, preflight reads the target project and reports every field as carried over, remapped, skipped or blocked, with the fix. If anything is blocked, nothing is created, so there is never a half-built epic to clean up.
No epic to start from? One button builds a starter template from your own project's issue types, so it is guaranteed to run.
One click from an epic to a template - Open any epic and choose Save as issue tree template. Child items, sub-tasks, their field values and the links between them are captured exactly as they are, and nothing in Jira is changed.
Preflight: know before you create - The app reads the target project first and reports every field as carried over, remapped, skipped or blocked, with the fix. If anything is blocked, nothing is created at all.
One template, every project - Templates live in the app, not in a shadow project. Draw links between work items, drop field values you do not want, and see how often each template is actually used.
No template picker inside Jira's own Create dialog. You start from the app's page, or from the work item you want to template.
A captured tree is limited to 200 work items and four levels deep.
Attachments are not copied.
There is no scheduled or recurring creation.
There is no undo. Preflight is designed to make one unnecessary; if a run does fail part-way, the app lists exactly which items were created.
Email support@maxpetrov.pp.ua and we will reply. Include the template name, the target project key, and what preflight reported. If a run was blocked, paste the blocked line: it names the field and the fix. If work items were created but look wrong, the issue type names in the template are the first thing to check, because they differ between company-managed and team-managed projects.