RFCs can be linked to form project Groups when Requests are related in some way (e.g., Requests that require the same action). New Groups must consist of Requests that are not already linked.
Creating a New Group via the Change Request Tab
From the Change Requests list under the Changes tab, tick the check boxes in the far left-hand column corresponding to unlinked Requests
Click Link to group the RFCs.
A Group Number will be assigned and an instant Group hyperlink will
appear under the Group column, if included in the List View.
To add RFCs to an existing group:
Within the Change Requests list, check the boxes of the new RFCs and at least one member of the Group to which you wish to add the RFC
Click Link.
This will not work if RFCs representing more than one group are included. For instance, if you have two Groups (A and B) each with two RFCs (A1, A2, B1and B2), and you want to add two unlinked RFCs to Group A, click the check boxes for the unlinked RFCs and either A1 or A2 or both. If B1or B2 is also clicked, the linking process will fail because it will not know which group to add the two new RFCs to.
Existing Change Groups can be merged within the Change Groups tab, to allow all related Requests within the Groups to be managed as one. To combine Change Groups:
Go to Change>Change Groups
Check the fields next to the relevant Group #'s
Click
Merge
The screen defaults to the Details tab for the Merge Group.
Set the Name, Item Type, Classification, Status, Priority and Description that best defines all associated Change Requests
Click
Save.
The History tab records details of the Groups merged to form the new
Group. Click the No. hyperlink to view the details. The Impact tab
records the Type and Number of requests associated with the Group.
RFCs that are included in a Change Group list the associated RFCs within the Related tab of the Change Summary tab. See Related.
Requests can be grouped by selecting the checkboxes next to the Task list, followed by the Link button.
The type of Request Group created is based on the Request type assigned to the Group.
If the Group contains Service Requests/Incidents, it is an Incident Group
If the Group contains Incidents/Problem, it is a grouped as a Problem
If the Group contains Service Requests/Change, it is a Change Group
If the Group contains Service Requests/Incidents/Problem/Change, it is a Change Group
If the Group contains Problem/Change, it is a Change Group.
As part of the Change Management Process, all requests related to a Change Request are automatically closed when the related RFC is closed. The system views the request hierarchy from low to high as Service Request, Incident, Problem and Change Request, and if a related request of a higher type is closed, all the lesser type requests are automatically closed, or if the handshaking facility is enabled for the system, moved to the Pending-Approval State.