Apps documentation
Issue Templates for Jira
Server/Data Center Cloud
Issue Templates for Jira

Server/Data Center

Cloud

Guides
FAQ
Release notes
Last updated Oct 26, 2018
Warning
This post function is active but no longer recommended. We encourage you to use the Create Structure post function in all new projects.

Copy from Epic

This section provides information on how to use Copy from Epic feature.

Issue Templates for Jira allows to create Epic templates with multiple stories and sub-tasks inside and use it in issues. The procedure of creating epic templates in repository is similar as in regular templates.

First of all:

  • you need to add Epic and Story to your project issue type scheme. Epic and story should be available in template’s repository as well as in project, where issues are created from template.
  • it’s also necessary to add Epic Name and Epic Link fields to target screens. Without them you may have problems with creating issue.
  • add Copy from Epic post function to target project’s workflow. Thanks to that, epic’s stories and sub-tasks will be copied as soon as issue is created.
    Note
    Copy from Epic post function supports only Jira Software.
    Info
    If you’re not sure how to add post function to a transition in workflow, click here.
    Info
    While configuring post function you can set the Stage for sub-task. This option allows to automatically generate a sub-task, when a template issue passes defined transition in workflow. Value from Copy from Epic stage must be the same as the one from sub-task template (Create conditions section). Read more about stages here.

How to create an Epic template?

Steps

  1. Create an epic template in your template’s repository and fill in necessary fields.
  2. Click Create.

    Your epic template is saved. Now, you are able to create stories.
  3. Click on ‘+’ in Issues in Epic.

  4. Select issue type from the drop down list and fill in fields.
  5. Click Create.

Result

All created tasks and stories are now available as regular templates. You can use them in the future as separate issue templates.

How to configure stories?

In Epic template’s structure, story has a separate Agile tab in Issue Templates Details section.

  • Issues, that are defined for Epic are available as a regular templates. To prevent using Epic’s issues as templates, switch the Only for Epic toggle to on.
    Note
    Epic templates should be used to create Epic issues.
  • Switch Copy Sub-task toggle to on to copy sub-tasks from story in template to a new issue.
  • With Create Criteria Query you can decide when epic’s stories will appear. Use the JQL function to set conditions for your stories.
    Example
    For example, you have created an epic template Business trip with two stories: Airline tickets and Company car. You’d like your first story Airline tickets to appear when user selects International Conference in parent’s single select Trip. In Create Criteria Query type JQL function Trip = International Conference. You’d like second story Company Car to appear when user selects National Conference. Your JQL function (condition) will be Trip = National Conference.
Note
Issues created from Epic template will have the same Story order as in the source template (unless you use conditions in Create Criteria Query).

Need help?

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.