For the Initiate milestone, in the Release form, use the Date/System tab in the Best Practice view to add the scheduled start and end dates for the release. These dates can also be revised for the Planning milestone. During deployment, you also use this tab to track actual and deployment start and end dates for the release.
The following information describes each of these date fields on the Release form:
Deployment Start Date
For the Deployment milestone, provide the date when the release starts to be deployed to the IT infrastructure.
Deployment End Date
For the Deployment milestone, provide the date when the release finishes deploying to the IT infrastructure.
Requested Availability Date
For the Planning milestone, provide the date and time when the release should be available.
The target date is the date by when the release must be completed, according to the applicable service level target. Alternatively, the target date can be a date that is agreed to on an ad hoc basis, per release.
On the Date/System tab, this field is read-only and is automatically set to the target date and time selected on the release form.
This field is read-only and is automatically set to the current date and time when the status of the release is set to Completed.
Scheduled Start Date
For the Initiate milestone, use this field to specify the date and time at which the release implementation is scheduled to start (the moment at which the release is planned to be set to the status Work in Progress).
Scheduled End Date
For the Initiate milestone, use this field to specify the date and time at which the release implementation is scheduled to be completed (the moment at which the release is planned to be set to the status Closed).
Important: Scheduled start date and end date values cannot be modified when the release is awaiting approval.
Actual Start Date
For the Deployment milestone, provide the date for when work started on the release.
Actual End Date
For the Deployment milestone, provide the date for when work ended for the release.
Release form — date information
You can use the Schedule Assist tool to identify possible conflicts associated with releases. You can search for windows of opportunity that your release request can be scheduled around. The Schedule Assist tool helps you search for available deployment times for the release request based on global business events and CI availability. When you create a release request that modifies a CI — for example, you must upgrade a server — you can schedule a time segment for the CI that shows it is unavailable to the rest of the support staff. If another member of the support staff wants that CI to be available, they should schedule their own release in a different time segment. You can perform the tasks listed in the following table.
The following processes are essentially the same for Change Management and Release Management, with one exception for the Schedule Assist tool. The Release form shows you the CIs related to the changes in the release manifest. In Change Management, you see the CIs that are directly related to the change.
Register unique business events for releases
For more information, see:
Registering CI time segments for releases
For more information, see:
Use Schedule Assist to search for available times
For more information, see Using Schedule Assist to search for available times