Skip to main content
Matrix42 Self-Service Help Center

Creating release templates

Overview

Most teams create release templates to simplify release configuration.

Adding a release template

To create a new release template, navigate to Release Management > Configuration > Release Templates, and then click Add release template. You will need to have the Release Management role to do this.

Release_management_release_template.png

When creating or editing a release template, you can edit the template's name and description, attach any relevant assets, click the Add release phase button to add a release phase, drag an existing phase vertically to re-order it, and hover over an existing release phase to Edit or Delete it.

Release phases come in two types: phases and milestones. Milestones are single important dates to your project — such as the date that design is completed, or the date that the app store approves your mobile application. Phases are containers of work within your release — you may have design, development, and test phases, for example. Both types of release phases are optional. Use this template to design a workflow that best helps your team.

Editing a release template

To edit a release template phase, hover over it and click Edit. You can add, edit, or delete the following details:

  • Name: The name of the phase or milestone.

  • Type: Select if this is a phase or a milestone. Remember, a phase represents a range of time with a start and end date, while a milestone represents one specific date.

  • Days after prior phase: Allows you to stagger your phases and milestones. Using a negative value here will allow you to define phase or milestone overlap in your template.

  • Change template: Used to configure automation for deployment that will be triggered by entering the phase.

  • Duration: The default duration allows you to specify how long each phase is. This is not applicable to milestones since milestones are a single specific date.

  • Color: Allows you to specify the color of the phase or milestone when visualized on roadmaps.

  • Trigger phase on status change (optional): Release will automatically enter a phase when status gets changed to defined one.

Default Release Template

The Default Release Template contains the Release Testing phase that is linked to the Release Management - Testing Release Phase change template and the Ready for Testing status.

When the release status is changed to Ready for Testing, the system will execute the corresponding workflow and a new change will be created with a set of tasks.

Tasks related to the change need to be closed as Directly solved in order for the release to automatically change its status to Ready for Shipment. If you close a task as Rejected, a problem will be created.

Release_management_change_templates.png

  • Was this article helpful?