Raising Changes

From Hornbill
Revision as of 16:53, 7 December 2015 by Stevenb (talk | contribs) (Created page with "__NOTOC__Home > Service Manager > Raising Changes ==Introduction== Change Management in Service Manager enables customer to manage changes to their IT infra...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Home > Service Manager > Raising Changes

Introduction

Change Management in Service Manager enables customer to manage changes to their IT infrastructure in a controlled manner in order to minimise risk.

Logging a Change

Changes can be raised in a number of different ways.

  • An analyst with a minimum of the Change Management Use role can raise a new Change record from the following places:
  • The Request List > Using the Raise Change drop down option next to the Raise New icon
  • Boards > Using the Raise Change drop down option next to the Raise New icon
  • Existing Incidents records > Using the Raise Change from the Raise New Linked Request option under the Link Action Bar or Using the Raise Change drop down option next to the Raise New icon
  • Existing Problem records > Using the Raise Change from the Raise New Linked Request option under the Link Action Bar or Using the Raise Change drop down option next to the Raise New icon

Changes can be raised against one or multiple assets during the logging process, by associating them using the Assets form in Progressive Capture.

Changes can be routed manually to the Change Management team or a specific individual using the Assignment form in Progressive Capture equally this can be automated using the Assign to Team or Assign to Analyst nodes in an underlying Business Process.