It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to Create an Epic Issue Template in Jira Cloud



Issue creation is one of the basic actions one can make in Jira. People usually spend a big chunk of their working time in this software, especially if they have to re-create the same Epic over and over again. Here's the detailed guide on how to avoid repeating this task manually with Issue Templates for Jira Cloud - the #1 solution for automating issue creation.

Project configuration

In the Configuration section of Add-ons → Issue Templates menu, you choose a project where you will store all your templates, or create it right from this screen if you haven't done it beforehand. If you change the repository project here, the configurations will be cleared, but the issues themselves will remain inside the project. It means that you won't have to re-create those issues if you want to restore later, but you will have to provide the specific parameters once again for every template to have them clearly visible on the list while creating an issue.

issue-templates-cloud-configuration.pngIf you create the repository project from this screen, it will probably use the brand new Agility board. If you then create a template via quick creation on such a board, it will have only a summary, so you'll have to edit it later anyway. That's why we recommend to turn off the board and use the Issue Navigator with the plus icon on the global side panel, which calls the full Create Issue screen.


Then, if you don't see the Epic issue type when creating a template, you have to add it to the project in the Issue types section of the Project settings.

issue-templates-cloud-issue-type-add.pngThe next step is to add the Epic Name field to your Create Issue screen, because otherwise you won't be able to create an Epic in this project. You can do it in the Screens section of the Project settings.


Then go to the Create screen, provide a name for your Epic along with all the required fields, and create the issue. After that, you need to set it up as a template.

Template configuration

Basically, templates are just like regular issues. The difference is that they have the Template Detail section added. The Template Name is different from the issue's summary - it is the name that will be shown on the template list when creating an issue, so it should be something descriptive to make it easier to find. A Scope is a set of fields that defines which values will be copied from your template to the target issue. The default Scope consists of just a summary and a description, but custom Scopes can also store values from non-text fields, like Assignee or Priority. As its name states, the Copy Subtasks toggle allows to copy the added sub-tasks altogether - their fields' values will be autocompleted as well.

You can choose different issue types for your custom templates, but you should always use the Epic issue type if you want to make an Epic template.


Then go to the bottom of the screen and click the little plus icon to create Stories or Tasks inside this Epic. You can go further and add one more level to the structure by choosing a Story and creating Sub-tasks via the three-dot menu on the upper right side of the screen. Remember to have the Copy subtasks toggle switched on, and check if a Scope for the Sub-tasks is defined - otherwise they won't be copied to the target issue.


Create issues

That's it! Now your users can create the whole Epic structure from a single template by choosing the Epic issue type and the right template, in under 10 seconds. Nice and easy.

Here's how it looks like:


Got interested? Try out Issue Templates for Jira Cloud for free on the Atlassian Marketplace.

Watch the full video tutorial for a comprehensive demo and further explanations about the app.

In case of any questions, drop us a line on LiveChat at our Support webpage, or book a live session on Calendly.

Also published on Deviniti blog and LinkedIn.


I've created an Epic template for SCRUM, but it does not keep the time estimates from linked stories. Is there a way for me to do that? One of the main reasons I want to create a template is to have the time estimates. 

Thank you


Hi @Doug Catiller ,

You can choose which fields to copy from the template by setting a Scope aka Set of fields in the Project Settings, and then choosing it on the Template Configuration panel on the issue view. Have you included the Time Estimate field into the Scope for your Epic template? Here's the detailed instruction on how to do it:


Log in or Sign up to comment
Community showcase
Published in Marketplace Apps & Integrations

Localize Smarter with the Transifex Integration for Bitbucket

Over 52% of internet users say obtaining information in their own language is more important than price and 75% of the world’s population doesn’t speak English. It’s no wonder then that successful gl...

255 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you