Linking a Business Object to a Change Request

a change request can be linked to an incident, problem, configuration item, service, or release to resolve any issues change requests created within an object are automatically linked incidents incidents, not problems, should be created for any issues that arise during the change process problems arise from the underlying root cause of one or more incidents or potential incidents; for this reason, you cannot create a new problem from a change request you can, however, view incidents that are linked to a problem from a change record problems an existing problem can get resolved when a change is implemented, so you can link an existing problem record to a change all configuration items and services linked to the problem record get linked to the change by a default search and link business rule releases when the change request is linked to a release, link the problem record from the change request to the release record a change request is usually scheduled to implement or deploy a configuration item through the release mechanism in , configuration items include physical assets as well as services during the change, the needs to ask which configuration items have been affected, how have they been affected, and which services are impacted by the affected configuration items for example, implementing a new microsoft exchange server (a configuration item) could potentially impact email services (a service) configuration item the can view the ci map to view the services that might be impacted by or impact the change baseline the can view the baseline of a configuration item before making the change the application records a baseline of the associated configuration item in the baseline comparison tab of the configuration item record and in the baseline tab of the change record when the change is in implemented status services impacted services that are related to the change need to be linked to the service tab of the release record when the change is linked to a release see linking configuration items and services to a release docid\ pmdyvwm4k1h7ykg8nglct by default, a validation on save business rule that the problem cannot be set to resolved or closed unless associated change records are set to "implemented", "closed", "canceled", "denied", or "deferred" your administrator can enable this rule for the business object, if needed log in to open the change workspace open the change record to link within the change request, click the business object tab (incident, problem, or release) a list of links is displayed, if any click link from the toolbar a list of business object records is displayed select a record, then click select the record is added to the list and links it to the change click save