---
title: "Templating & Templates"
canonical: "https://help.releasemanagement.app/space/RMC/1493008448/Templating%20%26%20Templates"
format: markdown
---
> Macro (include)

# Topics

> Macro (toc)

# Introduction

This section outlines templates we provide to speed up the process of various entities creation in Release Management App & Jira Cloud.  This functionality is available from “Templates“ menu of the board:

![image](media://c780077f-7f27-4973-b833-cd2a29148728)

# Package templates

## Defining template

By clicking on “Templates“ in board menu ribbon you will see all the created package templates for this board or an empty list if there are none.

### Create new and edit existing

To create a new one click on “Create template“ button

![image](media://347373bf-f66b-488c-aee0-ab5ad6e8a4c4)

to show template create/editing dialog.

To edit existing template just click on it

![image](media://fcb3044c-030d-4da3-b19d-d7f6f075e8c0)

to open same create/editing dialog with template properties defined.

### Defining template props

Template create/editing dialog has the following properties:

![image](media://dbf9505d-830c-4c7c-b346-bcfe43d540ff)

- **Package name** - name of the template to distinguish from the rest. This is also a default package name that will be used while creating if not overridden
- **Description** - description of the package that will be created from this template
- **Tags **- tags will be auto populated for respective packages
- **Start date offset** - offset of package start date from the one specified while creating the package
- **Release date offset** - offset of package release date from the one specified while creating the package
- **Versions** - predefined list of versions that will be created with package
- **Package milestones** - predefined list of milestones that will be created with package

#### Adding versions to package template

If you want to add a predefined list of versions to your package template click on add button in versions section of the template create/editing screen

![image](media://8a399d5c-9d58-4c49-822c-95f41d6e66af)

Add version dialog will popup with the following props:

![image](media://4771509c-3eb4-495b-9181-34e8599a0f51)

- **Project **- in which the fixVersion will be created (matches the list of projects from the board)
- **Version name** - name of the version
- **Description** - description of the version that will be created from this template
- **Tags **- tags will be auto populated for respective versions
- **Start date offset** - offset of version start date from the one specified while creating the package
- **Release date offset** - offset of version release date from the one specified while creating the package
- **Version milestones** - predefined list of milestones that will be created for this version while creating the  package

To add version milestones use inline editing to specify

![image](media://526bd6cb-e6fc-4254-8b46-962674622259)

- **Name **- of the Milestone
- **Date offset** - offset of Milestone Planned Achieved Date from the one specified while creating the package
- **Triggers** - if you want to auto-achieve by moving in specific column

#### Adding package milestones to package template

To add package milestones use inline editing to specify

![image](media://4d898ab2-7dc1-4edc-a21d-75940d4fde49)

- **Name **- of the Milestone
- **Date offset** - offset of Milestone Planned Achieved Date from the one specified while creating the package
- **Triggers** - if you want to auto-achieve by moving in specific column

## Creating package from template

To create package from template choose Create/[PACKAGE]Create from Template menu item available from Versions and Packages boards as well as Roadmap and Calendar views

![image](media://5f50ed99-8add-45b8-9b4e-aafe167174b1)

In the “Create package from template“ dialog you would need to specify:

![image](media://67696e84-6276-484b-acb3-dec0da404577)

- **Template **- that you plan to use
- **Start date **- that will become a baseline for all the offsets specified in the template, namely Start and Release Dates on package and versions as well as Planned Achieved Dates of all the milestones (for package and versions)
- **Package name** - otherwise template name will be used
- **Prefix/Suffix **- prefix/suffix clauses that will be added before/after package name and associated versions, *but not the milestones*

Before pushing “Create“ button we suggest to review the transcript of all the entities that will be created with their names and dates

![image](media://4b4d9fcd-fae0-4a65-b61c-1035fb96ec42)

# Version defaults

You can also define som default naming convention for your version as well as default decription template and list of pre-defined milestones. To do so, go to Board Settings / Version defaults section. Read more details here:

[https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92078312/Configure+board+settings#Version-defaults](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92078312/Configure+board+settings#Version-defaults) 

> Macro (include)