A template set usually creates its whole structure, top to bottom: the epic, its work items and their subtasks. That’s right when the work is new. But often the epic already exists. A product manager created it during planning, or it came from a roadmap, and now you want the standard work under it.
Version 27.0.0 of Epic & Issue Templates, released June 29, 2026, handles that case.
What changed
When you apply a template set, you can now pick an existing epic or feature as the parent. The set adds its child work items under the one you picked, instead of creating a new epic.
The same release shows email addresses next to names in user lists, so you can tell two people with the same name apart when you pick an assignee.
When to use it
- Feature work. The epic comes from planning. Apply your “feature delivery” set under it to add spec, build, test and release work items.
- Customer projects. The epic is the customer engagement. Apply the kickoff set under it.
- Incidents. The epic is the incident. Apply the follow-up set under it for the review and action items.
How to do it
- Open the app and pick the template set.
- Choose to apply it, and pick the existing epic or feature as the parent.
- Fill in any variables the set asks for.
- Apply. The child work items appear under the epic you picked.
Why it matters
Templates should fit how teams already work. Planning usually happens at the epic level, and the detailed work comes later. Now the template set can join the work at the level where it starts, instead of forcing a new epic.



