Release Requests: Difference between revisions
Line 37: | Line 37: | ||
:* '''[[Link Action Item|Link]]''' | :* '''[[Link Action Item|Link]]''' | ||
:: Link this request to other requests | :: Link this request to other requests | ||
:* '''[[Linked_Services_Action_Item|Linked Services]]''' | |||
:: Link other related Services to the request | |||
:* '''[[Authorisation Action Item|Authorisers]] | :* '''[[Authorisation Action Item|Authorisers]] | ||
:: Add Authorisers to a Reqeust | :: Add Authorisers to a Reqeust |
Revision as of 13:36, 16 June 2017
Home > Service Manager > Requests -> Release Requests
IntroductionRelease Management helps facilitate the release of one or more related changes. A number of different tools are provided to help you record information against the release, communicate with the connected uses, and collaborate with your co-workers. Scheduled Releases are added to the Change Calendar to help with planning and identifying conflicts. |
Related Articles |
Features
Heads-Up Display
The Heads-Up Display is a graphical representation of the business process that supports the Release process. 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 Release. These actions are placed near the top of the Release form and collected together to allow for quick access to update the Release. The available Actions can be either made visible or hidden for different types of Releases, based on the Service they are associated to. The supporting Business Process Workflow that sits behind the Release 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
Located at the top right of the request form, this provides some on hand information about the request including the team and person that the request is assigned to, the status, when it was raised, what the priority is, and if the request is under a Service Level Agreement the Service Targets will be displayed.
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 contact information.
Details
Capture, view, and update the Summary and Details of the request.
Timeline
The Timeline keeps track of all the history of the request. Use the Filter to show updates of a specific type. Comment and collaborate on any update that has been made.
Members
The Members feature lets you invite people into a request who may not normally have access. Adding a user as a member will notify them that they have been added. Once added they will be able to see the request as if they were part of the team.
Activities
Activities can consist of Activities that have been automatically created and assigned as part of a BPM workflow or at any point a support person can manually add an activity to schedule any work that they are going to do.