This documentation applies to the 8.1 version of Change Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Working with release relationships

You can use the Relationships tab to create associations between releases and other application objects, for example, CI unavailability, configuration items, incidents, infrastructure changes, known errors, LDAP objects, problem investigations, other releases, and software library items. Relating application objects (such as CIs) to the release request lets you identify items that the Release Coordinator plans to address in the release.

The relations in a release request are informational only, and are not required to be part of any milestone of the release request. In addition, the application objects do not have to be Completed or Closed for this release to be Closed.

For more information on creating a relationship, see Defining relationships.


Change requests or activities that are necessary to implement and close the release are added as release manifests. These are tied to a milestone of the release and must be completed during that milestone for the release to move to the next stage. For more information, see Creating a manifest.

Release form — Relationships tab

For more more information, see Working with relationships. The information about relationships in the context of change requests applies equally to release requests. Where exceptions exist, these are noted.

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