Skip to main content
Matrix42 Self-Service Help Center

Release Management


Release Management involves outlining crucial phases of work upfront. That includes everything from feature definition to testing and other necessary day-to-day activities. Release Management application guarantees smoother releases and fewer complications, thus you can deliver software faster and provide a better customer experience.

A strong release management process keeps your team focused and aligned around a consistent set of criteria, so that everyone involved knows what is expected to be done, how, and when. This process is fulfilled by the components of the Release Management application that are described below.

This functionality will be made available soon as a package on our Matrix42 Extension Gallery. 

Home page

The Home page provides a bird's-eye view of the key information about the planned releases by month, their status, and related tasks.



Use the Products section to manage a list of products: create and describe its purpose, assign Responsible Team, Product Owner, and set Deployment Type(s).

Add Releases so that they are transformed in a Roadmap on the Product preview:




Release plays an important role in joining the gap between the project activities and the tangible modules and software services that product teams produce and deliver with every new roll-out of the product.

The Releases section provides a list and a detailed view of the release state, related information like Problems, Tasks, Changes, included features, and other relevant information:


Apply Release Template

It is possible to apply Release Template for the release. Depending on the Release Planned GA date, release phases will be automatically calculated and added to the release

Release template is displayed as Gantt diagram at release's preview


Every Feature is a part of a defined Product and is delivered in a specified Release. Additionally, you can add Tasks that are related to this feature or report Tickets or Problems that occurred due to this feature.

Edit the Feature and set the Status to see the overall progress on the board:


Change Requests




Changes are normally used for automated phases of the release lifecycle

For instance, when using  "Default Release Template " the Phase "Release Testing"  is linked to the "Release Management - Testing Release Phase" Change template

When Release status is changed to "Ready for Testing" the system will create a new Change and start the process of validation automatically

A new Change will have a list of tasks. The actor needs to Close the task that is related to change that is related to release as Directly solved- > Release will automatically change the status to Ready for Shipment. Otherwise close task as Rejected - Problem will be created

When the Validation state ends - release status will be changed to "Ready for Shipment" which will trigger the next phase - Deployment


Release Management provides the following Reports that can be generated from the data available in this application:

  • Overview Release List includes a product-specific list of releases, information about their status, type, priority, and planned end date

Release-Details requires a release number or code (e.g. REL00002).


Click on the Report for more details. Each report has a set of specific filters depending on the type of the report. 

Set necessary filters and click View Report to generate and load the data:



Release Templates

Most teams create release templates to simplify release configuration

Add Release Template

To create a new release template, navigate to either Release Management → Configuration⚙️ → Release Templates, then click Add release template. You will need to be in Release Management Role to do this.


When creating or editing a release template, you can edit the template's Name and Description, attach any relevant assets, click 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.

When adding phases and milestones, you will be presented with a few options:

Edit a release template

To edit a release template, hover over it and click Edit. From the release template details, you can add, edit, or delete template details following the same functionality listed above.

  • 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 Phase "Release Testing" that is linked to "Release Management - Testing Release Phase" Change template and status "Ready for Testing" when Testing phase will start automatically.

When Release status is changed to "Ready for Testing" the system will execute the corresponding Workflow: a new Change will be created with a test of tasks. Close task that is related to change that is related to release as Directly solved- > Release will automatically change status to Ready for Shipment. Otherwise close task as Rejected - Problem will be created




  • Was this article helpful?