1. Field Service Guide
  2. Process Flow for Creating Patch Requests

Process Flow for Creating Patch Requests

After users close change requests (CRs) as verified, the release management group might determine that they must provide a CR fix to a customer immediately and not in the next release of the product. The following figure shows the process flow for the tasks in patch request creation.

Process Flow for Patch Request Creation. This image is described in surrounding text.

More information about the tasks in this process follows:

  1. Find Verified Change Request with Urgent Customer Need for Fix. A member of the release management group identifies a closed and verified CR that represents a resolution for which a customer cannot wait until the next scheduled release to receive.

  2. Generate Patch Request from Change Request. A release manager generates a patch request (PR) from a CR. For more information, see Generating Patch Requests from Change Requests.

  3. Get Approvals. The release manager obtains the approvals necessary for shipping the patch, and records the approvals in the PR record. For more information, see Approving and Shipping Patch Requests.

  4. Retest. If all approvers do not agree that the patch is ready to ship, then the release manager sends the patch back to engineering for further development, testing, and another approval cycle.

  5. Ship Maintenance Release. After the release manager gathers all the approvals for the PR, the maintenance release is ready to ship to the customer. For more information, see Approving and Shipping Patch Requests.