Space banner

   

This documentation supports the 19.11 version of BMC Change Management, which is available only to BMC Helix subscribers (SaaS).

To view an earlier version, select the version from the Product version menu.

Relating ad hoc tasks to change requests

You can relate an ad hoc task to the change request. The status of these tasks can be Staged, Assigned, Pending, Work in Progress, or Closed. You can manually set the assignment for any task. Finally, if you close the task, you must select whether you are canceling the task or completing it as a success or failure.

When you relate an ad hoc task to a change request, the following information from the change request get populated in the task.

  • Summary
  • Change location
  • Requester
  • Requested by

To relate an ad hoc task to a change request

  1. Open the change request, and then click the Tasks tab.
  2. In the Request Type field, select Ad hoc, and then click Relate.
    The Task form appears with certain fields in the form filled with data from the change request. You can click the Open link next to the Request ID field to open the parent change request.
  3. Fill in the following required fields:
    • Name—Enter a descriptive name of the task.
    • Summary—Enter a brief description of the task.
      The Type field is set by default to Manual when you create an ad hoc task.
  4. In the General tab, fill in information about the company.
    The Company field defaults to the contents of the Change Location field in the Change form. Your task can be assigned to a different department or company.
  5. On the Requester tab, enter information about the person defining the task (Requester) and the intended target of the task (Requested For).

    Important

    If you update the Requested For information after creating a task for change request, the information is not updated in the task.

    However, any new tasks after the update, include the updated Requested For information.

    Some information is filled by default from the Requested By information of the change request.

  6. In the Categorization tab, fill in information about the product and operational categorizations.
  7. In the Assignment/Dates tab, fill in the following fields to assign the task:
    • Assignee Group—Optionally, select a task implementer group from the list.
    • Assignee—Optionally, select a task implementer from the list.
      The assignment engine automatically assigns the task when the task is generated. You can override this if needed by manually assigned the task.

      Important

      When a task is assigned to a user, the task is staged but the notification is not sent to the assignee until the task is activated.

      For more information about assignment configuration, see Configuring task assignments.

    • Scheduled Start Date—Optionally, enter an estimated start date.
    • Scheduled End Date—Optionally, enter an estimated end date.
      You might want to set the Start Date and End Date to be different from the dates of the parent change request.
  8. In the Relationships tab, search for and then relate configuration items, LDAP objects, and software library items that are needed with this task.
    Additionally, you can execute any quick actions like Update Attributes, Explore CI or get Related Relationships for the task.
  9. When you finish creating the task, click Save.
  10. To specify if you want to notify the assignee or not, reopen the task and in the Assignment tab, select the appropriate option from the Notify Assignee field.

Important

You must save and reopen the task to add Work Info details or attachments.

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

Comments