Creating a release without a template
If your system does not have templates defined, use this procedure to create a release. Before creating a release, ensure that the change requests that you want to link to the release are created.
To create a release without a template
- Click the Remedyforce Console tab.
- From the View menu, select Releases and click New.
- In the Release Title field, enter the release title.
Enter other information about the release, and click Save.
For more information, see Release fields.
When a record is created, the following action is recorded in the Release History section that tracks the date and time when a record is created and the user details:Changed Status to Opened Created
By default, record details for incidents and problems are not provided on the release details page. Contact your system administrators to customize the layout of the release details page to display the Linked Incidents and Linked Problems record details.
Release fields
The following table describes the fields that are available on the New Release form and the actions that you have to perform. Based on the layout that is assigned to your profile, some of the fields described in the table might not be available on the New Release form that is displayed to you. Common items are displayed on the form. For more information, see Common items on forms in the Salesforce page layout.
Your system administrator can apply filters to a lookup field on the Release form. Here are a few important points that help you understand the lookup filters.
- If a filter is applied to a lookup field, only the records that match the filter criteria are shown in the pop-up window. If the configured filter is optional, you can use the Show all results option to remove the filter.
- Type ahead in the lookup type fields works only on the results that are the part of the filtered results. For example, on the Category lookup field, if a filter is applied to show only Hardware and Applications as the results, then type ahead only works for those two categories. Also, if you click the lookup icon to search for the other categories by typing in the search field, the search does not return any results unless you use the Show all results option to remove the filter.
- If your system administrator has configured a custom lookup field, the type ahead functionality does not work when you are using the field for the first time. You must click the lookup icon and select the required option for the first time.
Field | Description |
|---|---|
Release Details | |
Release Title | Enter a title for the release. |
Description | Type a description of the release that you want to implement. |
Template | Select a template to apply to the release. When you click Save, the values of the fields in the template are filled in the corresponding fields of the Release form. To help ensure accuracy and completeness, BMC recommends that you use a template to create a release record. A template ensures consistency in the way information about the release is captured. Your administrator can define templates for commonly occurring releases. |
Category | Select a category for the release. Categories enable you to classify the release by using standard classifications, which can be tracked for reporting purposes. After you save the record, |
Release Type | Select the type of release from one of the following options: Major -- The release includes new features or significant changes to existing functionality. Minor -- The release includes smaller updates to existing functionality and emergency fixes that were previously delivered to the customers. Emergency -- The release includes fixes for urgent issues that have a critical impact on a customer's environment. |
Subtype | Select the subtype of the release from one of the following options: Backlog -- The release is being planned and implementation activities have not yet started. Delta -- The release includes only the product components or files that have changed since the previous release. Full -- The release includes all the product components or files, including those that have not changed since the previous release. Package -- The release includes a set of related full or delta releases. |
Deployment Type | Select the method of deploying the release from one of the following options: Phased -- The release is initially rolled out to a smaller group of users and then subsequently to all the users. Non-phased -- The release is rolled out to all users at the same time. |
Release Coordinator | Select the coordinator of the release. |
Testing Completed | Update this date when all the tasks of type Testing are closed in the manifest. Ensure that all the tasks that have the Testing value in the Task Type field are closed. Also, all the Task Type field can be used when you are creating a task in the release templates. |
Status and Priority Details | |
Impact | Select the impact that you want to assign to the release. |
Urgency | Select the urgency that you want to assign to the release. |
Priority | The priority of a record is calculated from the values for impact and urgency and is displayed in this field. |
Status | Select the status that you want to assign to the release. You can track the progress of a release through its stages by using this field. |
Date and Time Details | |
Due Date | Select the due date of the release. |
Completion Date | Select the date on which the release is complete. |
Start Implementation | Select the date when you plan to begin implementation of the release. |
Actual Implementation Start | Select the date on which the release implementation started. |
End Implementation | Select the date on which end of the release implementation is planned. |
Actual Implementation End | Select the date on which the release implementation ended. |
Start Deployment | Select the date when you plan to deploy the release in the production environment. |
Actual Deployment Start | Select the date on which the release deployment started. |
End Deployment | Select the date on which the end of the release deployment is planned. |
Actual Deployment End | Select the date on which the release deployment ended. |
Business and Financial Details | |
Budget Available | If the budget is available for the release, select the check box. |
Business Justification | Select the business justification for the release. |
Comments | Type remarks for the release. |
Risk Rating | Select the risk rating of the release. |
Required Contracts Verified | If you have verified the contracts required for the release, select the check box. |
Required Licenses Verified | If you have verified the licenses required for the release, select the check box. |
Required CIs Available | If the configuration items required for the release are available, select the check box. |
Assignment Details | |
Owner | The name of the logged-on user who creates the release is displayed in this field. You can change the owner of the release after saving it. For more information about changing release assignment, see Changing the release owner. |
Comments
Log in or register to comment.