Associating RFCs with Release Trains

When planning release trains, you can associate requests for change with them. RFCs represent operational changes that may affect multiple applications or implement system infrastructure changes within an enterprise. These are typically associated with tickets from service management systems such as Serena Service Manager.

The default implementation of Serena Release Manager includes a two-way integration with Serena Service Manager (SSM) that is driven by Serena Release Manager.

Adding RFCs to Release Trains

You may add existing approved infrastructure change requests from SSM to a release train as RFCs to track them as part of your release planning process.

You can add a request for change only when the release train is in a state for which this action is implemented. In the default workflow, a request for change can be added to the release train only when the release train is in the Planning state.

To associate requests for change with a release train:

1. View a release train and select the Requests For Change tab.

2. Click Add requests for change.

   By default, only change requests in Approved and Approved Changes states are listed for selection.

3. Select one or more requests for change to add to the release train.

4. Click OK.

Creating RFCs from Release Trains

You may find during the release planning process that an infrastructure change is necessary. You can create a request for change in SSM directly from a release train so that you don't need to invoke SSM separately for this purpose.

By default, you can create RFCs only when the release train is in the Planning state.

To create a request for change from a release train:

1. View a release train and select the Requests for change tab.

2. Click Create request for change.

   The SSM user interface form for creating an RFC appears.

3. Create the RFC using the SSM form.

   As you create the RFC, you may assign it to this release train using the Planned Releases tab. SSM will submit it to the Approved Changes state so that it will then appear under this release train's RFCs.

   If you create the RFC and don't assign it to this release train using the Planned Releases tab, it will not appear under this release train. You can later add it to this or another release train using the Add requests for change option.

4. Click OK.

Removing RFCs from Release Trains

You may find during the release planning process that an infrastructure change needs to be removed from a particular release train.

You can remove a request for change only when the release train is in a state for which this action is implemented. In the default workflow, a request for change can be removed from the release train only when the release train is in the Planning state.

To remove requests for change from a release train:

1. View a release train and select the Requests for change tab.

2. Select one or more requests for change.

3. Click Remove request for change.

4. Click OK.