Working with activity assignments
Your responsibility as a release coordinator is to properly assign the activity. If an assignment definition has not been created for the activity, you must assign the activity manually. Otherwise, the best practice is to use the assignment rules already configured for you by your Release Management administrator.
The activity assignee is then notified of activity assignments by email, pager, or BMC Remedy Alert. Assigned activities can also be listed in the Assigned Work Orders table in the console.
Activity assignment is based on the activity's categorization. The Assignment tab displays information about people assigned to an activity as the Request Manager or Request Assignee.
You must define at least one individual with the Request Manager functional role before you can make any assignments to a Support Group.
During configuration, the administrator determines to whom the activities are assigned. This decision is based on criteria such as the activity's categorization. For example, all activities that are categorized as hardware issues might be assigned to the Support-Hardware group. All activities that are categorized as software upgrades and originate from California might be assigned to Sonya Software in Santa Clara. The criteria of the activity together with the application administrator's configuration determines to whom each activity is assigned.
The assignee must make sure that the assignment is correct and accept the activity. If the assignment is not correct, the request manager can reassign the request.
These assignments are based on routing information stored in the Assignment Configuration form. This form assigns the groups and then Auto Assign assigns the individual. For more information, see Configuring assignments in the BMC Remedy ITSM Suite documentation.
The following topics provide more information about working with activity assignments: