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.
To view the Release Form, navigate to Admin > Release Management > Release Form and the below page appears.
The page displays two types of fields:
- Default Fields: These are the primary fields that come with the fresh installation. The field names can neither be changed nor deleted.
- Custom Fields: These are the additional fields added from the pallet. You can rename and delete them.
Here, you can customize the form using the below options:
- Field Pallet: You can drag and drop the fields from the pallet to add into the form.
- Re-Order: You can drag and drop the fields to change the order of the form. This option is available for both: default and custom fields.
- Duplicate: You can create duplicate fields from the custom fields. This option is available only for custom fields.
- Edit: You can edit the fields and make them mandatory, show on release form, or change their characteristics. For default fields, some of the options are restricted.
- Remove: You can delete the custom fields and not the default ones.
Deleting the custom field will remove it and its data from all the related requests. Also, the Workflows, Scenarios, SLAs, and other components containing these custom fields might be affected. Kindly review the impact before proceeding with the removal.
Example Scenario: For example, every release in an organization requires a version for the new release. This is the version by which a Release Manager and other Teams can identify the updated version of the upcoming release.
Text Input
To add the Text Input custom field, drag and drop it on the form in the right-hand side, and a popup appears.
Enter the following details:
Parameter | Description |
---|---|
Name | Enter the name of the field. |
Hint Text | Enter the text to appear by default. It appears in grey color. |
Default Value | Enter the default value of the field. |
Required | Enable to make the field mandatory on the release form. |
Release Stage | Select the stage at which the field should be available in the More Details section of Release Details page. The options are: - All: If selected the parameter will be available at the time of release creation. - Submitted: If selected you can edit the field only in the Submitted stage. During other stages it will be non-editable. - Planning: If selected you can edit the field only in the Planning stage as shown in the below figure. During other stages the field will be non-editable. - Build: If selected you can edit the field only in the Build stage. During other stages it will be non-editable. - Testing: If selected you can edit the field only in the Testing stage. During other stages it will be non-editable. - Deployment: If selected you can edit the field only in the Deployment stage. During other stages it will be non-editable. - Review: If selected you can edit the field only in the Review stage. During other stages it will be non-editable. |
Once done, click Add. You can then re-arrange its location, create a duplicate field, edit, or delete it if required. Similarly, you can add other custom fields. For more details on other fields, refer to the link Request Form.
System Fields like Location, Category, Department, Release Reason, and Business Services can be hidden, by enabling the Hide option as shown below. Once enabled, the field will not be available at the time of release creation.