Difference between revisions of "Change Requests"

From Hornbill
Jump to navigation Jump to search
Line 1: Line 1:
 
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;">
 
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;">
__NOTOC__[[Main Page|Home]] > [[Service Manager]] > [[Service Manager Request Types|Requests]] -> Release Requests
+
__NOTOC__[[Main Page|Home]] > [[Service Manager]] > [[Service Manager Request Types|Requests]] -> Change Requests
 
</div>
 
</div>
 
{|style="width: 100%"
 
{|style="width: 100%"

Revision as of 13:48, 16 June 2017

Home > Service Manager > Requests -> Change Requests

Introduction

The Change Request form is used to formally manage changes in the environment. A number of different tools are provided to help you record information against the Change, communicate with the connected customers, and collaborate with your co-workers.

Related Articles

Features

Heads-Up Display

The Heads-Up Display is a graphical representation of the business process that support the Change. This is an optional display which uses the stages and checkpoints within a process to visualize the progress.

  • The entire process is displayed as a grey bar with circles representing the different stages
  • The active stage is represented by a large green circle followed by a connector to the next stage
  • The connector will progressively turn green until the next stage is reached
  • Checkpoints are displayed below each stage
  • Grey Checkpoints are yet to be completed
  • Completed Checkpoints are represented with a green check mark
  • The Heads-up Display shows just the Stages, and when the mouse if moved over the Heads-up Display, the Checkpoints are exposed
  • The Heads-up Display can be Pinned to make the display of the Checkpoints persistent on all Incidents

Action Bar

The Action Bar contains the majority of functions that you can apply to a Change. These actions are placed near the top of the Change form and collected together to allow for quick access to update the Change. The available Actions can be either made visible or hidden for different types of Changes, based on the Service they are associated to. The supporting Business Process Workflow that sits behind the Change can enforce the display of an action when that action is required to be completed.


The Update Action within a request is used for posting information into the Timeline which can be used for collaborating with your team members.
Add images, documents, pdfs, and more directly to this request
Link this request to other requests
Link other related Services to the request
Add Authorisers to a Reqeust
Send an email directly from the request
Reassign the request to another team or user
Add other users that might have an interested in this request and keep them updated by email
Reset the Priority for this request
Associate One or more assets to this request
See what Boards this request is on or add it to a Board
Schedule this request and have it available on the Change Calender
Capture resolution details
Raised by mistake? Use this option to cancel a request

Information Box

Customer

If a customer is added to the request, a customer collapsable section will be visible on the request containing the following contact information about the customer.

  • Name (Handle)
  • ID (Link to profile)
  • Organisation
  • Email
  • Phone
  • Mobile

Remove

If it is required a customer can be removed from the request by selecting the Remove option in the Customer Details section. A timeline update will reflect this action.

Raised By

When a request is raised, the analyst who raised it, is added to the Raised By collapsable section of the request. This section contains their following contact information.

  • Name (Handle)
  • ID (Link to profile)
  • Organisation
  • Email
  • Phone
  • Mobile

Details

Timeline

Members

Activities