Learn how to apply templates to issues created in one project
With Create Structure you can choose between two ways of applying a template:
In both cases you’ll need to prepare your structure of templates beforehand. So, if you need an epic with stories and subtasks, just create that model structure within the Template Repository project (TEMP). Give it a recognizable template name, in order to find it easily back at this point.
If your template is an epic with stories and subtasks, then while creating that epic, the stories and subtasks will be created automatically. All field values you’ve provided in your template will be copied into the right fields in the target issue, too.
Create Structure will always create the entire structure of issues and override the availability settings of the particular issues. For example, when a story is set as unavailable it only means that it won’t be selectable within the Template field. However, when its parent epic gets created using the post function, the story will be created as well.
You’ll find more information about the post function parameteres and all possible configuration modes in the Create Structure configuration chapter.
To enable choosing templates for newly created issues:
Remember to add the Template custom field to the relevant screen.
Users can select a template from a custom field on the Create screen.
This mode is best for workflows where you don’t want to show users the Template custom field on the Create or transition screen. Otherwise, they might try to choose a template but they never will, because a template once selected in the post function will be applied every time and can’t be changed.
To apply a fixed template to all new issues created in your chosen workflow:
The chosen template is always applied to new issues created in the workflow.
If you can’t find the answer you need in our documentation, raise a support request.
