Space banner

 

This documentation supports the 19.08 version of Change Management.

To view an earlier version, select the version from the Product version menu.

Benefits of Best Practice view in the Release Management module

The following table describes the benefits of the Best Practice view in the Release Management module of Change Management.

Important

In the table that follows, the Navigation pane links are not mentioned if they are available from the Navigation pane, even if the link is accessed from a different group on the Navigation pane.

Benefits to the Best Practice view of the Release Management form

Feature

Best Practice view

Benefits

Assignment

Fields on Main view:

Coordinator Group

  • Type ahead
  • Menu button enables selection of group using organizational structure
  • Tooltip displaying organizational structure
    Release Coordinator
  • Type ahead
  • Tooltip displaying Name, Email, Telephone, and Site

Key information for managing release requests includes knowing which group and which person is responsible for coordinating the release until it is closed.

Best practice recommends that that the release coordinator is the same person who creates the release request. This is why these fields are automatically completed with the submitter's information if that person has the functional role of Release Coordinator.

If you leave the fields blank, the Assignment rules determine the field values after the submission.

Release Location

Fields on Main view:

Release Location

  • Type ahead
  • Tooltip
  • This field shows the lowest level of location information of the release coordinator.

Key release management information includes knowing where the release is coordinated from. The application also uses this field to determine access rights for multitenancy implementations.

Service

Field on Main view:

Service

  • Type ahead
  • Field label link opens the Service CI
  • View Business Service icon allows you to display configuration details of the selected service
  • Service context widget, which can be launched to display essential status info about the selected service

This field was moved to the Main view, because the information it contains is considered key information.

Out-of-the-box, the Service field is a required field. This ensures that service awareness is used for routing purposes and metrics can be tracked by the selected Service. However, you can configure the field to not be required.

Template

Field on Main view:

Template

  • Type ahead, searchable

Adding the Template field to the Main view encourages the use of templates and enables you to search and report on the changes created by template.

Notes

Field on Main view:

Notes

The Notes field contains key release information.

Business Justification

Field on Main view:

Business Justification

  • Required

The Business Justification field contains key release information.

Target Date
(introduced in release 7.6.00 of BMC Remedy ITSM Suite)

Field on Main view:

Target Date

The Target Date is part of the key release information.

The Target Date is the date by when the release must be completed, according to the applicable service level targets. Alternatively, the target date can be a date that is agreed to on an ad hoc basis, for each release.

Work Info

Fields and table on Work Detail tab (shown initially):

Notes
First attachment
Additional fields hidden in More Details expand area:
Work Info type
2nd and 3rd attachments
Locked
View Access

Key release information includes Work Info entries.

Release Type

Field on Main view

The Release Type is used to identify the type of release that is being handled.

Requester

Fields not available

Best practice recommends that you review the related incident requests or known errors, or both, to determine who requested the release. The release could have been requested by multiple people.

Time Spent

Field on Date/System tab:

Cumulative Efforts

The Cumulative Efforts field was added in preparation for the automatic roll-up of time tracked in related activities and changes.

Approval

Table on Main view (Work Detail tab)

The Approvers table contains key release information.

Operational Categorization

Fields available for quick selection using the Select Operational link under Quick Actions.

Customers can view all operational and product categorization values using the Categorization links.

Research suggested that most BMC customers use the operational categorization fields only sporadically. This means that even when the fields are completed, they cannot be used for reporting, because they are not consistently completed.

Based on this, access to the fields was moved to a tab, which you configure to appear or be hidden, according to your organization's needs.

You can specify the operational categorization values for each template.

Product Categorization

Fields on Categorization tab (if configured to be displayed):

  • Tier 1
  • Tier 2
  • Tier 3
  • Product Name
  • Model/Version
  • Manufacturer
    Type-ahead available for all fields. Auto-complete and prefill available for Product Name

These fields were moved to the Navigation pane, because using the CMDB is a better way to perform grouping, trending, and assignment. This, and wanting to reduce the registration time of new incident request records, means that now the product categorization is automatically completed based on the product categorization of the related service.

Financials

Available as a link under Links

Nonessential information is moved to other areas, providing a more streamlined application.

Dates

Fields on the Date/System tab with the exception of Actual Start Date and Actual End Date

The two date fields are not considered essential for the release resolution or for reporting purposes.

Next Stage

The Next Stage button was introduced in the Best Practice view.

These buttons were added to increase efficiency.

Read-only behavior

When you do not have modify access, the following message is displayed at the top of the form:

You do not have permission to modify this ticket.

The fields are not disabled or read-only, but you cannot save any modifications.

This aids with simplification and enhances performance.

Was this page helpful? Yes No Submitting... Thank you

Comments