Page tree

Template (Epic) Cloner for JIRA

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

New custom field

During installation process, new custom field is added to your JIRA instance. 

After installation process, new position Template issue is available on Custom fields list like on picture below.

This custom field can be added to any create and edit screens where users could tick JIRA issue as a template.

Adding Template Issue custom field to your screens is not mandatory.

Template (Epic) Cloner for JIRA will work without this but is highly recommended to use it.

If you add this field to your screens, you will be able to filter templates and production issues in easy way.

Template creation

Template is composed of:

  • One Epic issue,
  • Any issues of any types linked to the Epic (relation “Epic link”),
  • Any sub-tasks in the Epic,
  • Any sub-tasks in issues linked to the Epic.

Example of Epic template looks like below:

To create issues linked to Epic you can use any issues type you have configured in your JIRA instance.

Issues in Epic can belong to any JIRA projects crated in your JIRA instance.

How to create Epic and link issues with epic you can find on Atlassian Jira Epics Tutorial.

More about sub-tasks you can read on Atlassian support page.


  • No labels