- Get started
- About
- Glossary
- First steps
- Migration to Cloud
- Integrations points
- Create issue from template
- Recreate issue
- Apply template
- Apply template post function
- Legacy automation action
- Template custom field on issue create screen
- Apply template via issue property
- Configuration
- Repository
- Template's configuration
- Using templates
- Copy Epic
- Copy links and linked issues
- Copy Subtasks
- Copy Initiatives
- Default templates
- Using Variables
- Static variables
- Dynamic variables
- Smart defaults
- Basics
- Smart issues
- Smart users
- Smart dates
- Smart project
- How to use smart defaults
- Security
- Security statement
- App permissions
Copy Epic
This page provides information how to create templates for epics.
Issue Templates for Jira app allows you to copy and link stories to an epic without any additional configuration. The app rewrites links automatically, so that they are pointing to newly created stories/issues instead of templates.
In Create dialogs, you can select different issue type than the one set in the template. However, in case of using epic templates, you should always select an epic issue type.
Thanks to that, the primary template and its stories will be linked properly.
Epic Link field
Epic link serves a purpose to link parent ↔︎ child relations and it is set by Issue Templates when child issues of the epic template are created. It is always rewritten to point to a new parent and match new hierarchy.
When you apply a template to a story, and your template points to an epic that is not a template, then if Epic Link is in scope it will be copied exactly at it is. In this scenario, if Epic Link points to template, it won’t be copied.
If you can’t find the answer you need in our documentation, raise a support request*.
*Include as much information as possible to help our support team resolve your issue faster.
