📄️ Overview
The Release management group has the options that are specific to customize the Release module. It has following features:
📄️ Release Form
The layout of release management has all the fields required to manage the releases of an organization. However, to meet the organization’s needs, you can modify the default template and add new fields. The fields can later be used in the automation settings also.
📄️ Release Status
Release Status determines the progress of the Release tickets at each stage. Using these you can know how much work is done or pending on the ticket and accordingly actions can be taken. The system provides some default status values that are ready for use.
📄️ Release Categories
Categories enable you to bring the similar releases under a single group. This helps the technicians in filtering out the required releases easily and quickly from a huge list. The system provides the below categories by default:
📄️ Release Type
Release Type determines the kind of release that is requested. It is another set of classification that helps technician filter the releases.
📄️ Release Risk
Release Risk shows the risk factor involved which would affect the release adversely. There are pre-defined levels of risk mentioned in the system by default which cannot be removed.
📄️ Release Reason
Release can be defined based on a specific reason which leads for the improvement in existing instances. This development or improvement can be called as a Reason for the Release.
📄️ Release Templates
Templates are ready-made forms which can be used while filling up the release form. The user only needs to select them and the form will get automatically filled. These are convenient when a release is of standard or recurring type. The advantages of using a template are:
📄️ Release Custom Rules
The custom rules help you to enforce the organization’s compliance while processing a release. Using these rules you can ensure that any change in the release attributes is supported by proper comments or notes. For example, a release should not move to the approved state if there is no manager assigned to the release. Similarly, you can use custom rules to enforce the approval workflows and closing tasks to close a release.
📄️ Release Model
A Transition Model is a concept that describes how a Release ticket transits from one state to another in ServiceOps.