ITSM use case: Change management standard change


Scenario  

The ITSM team needs to make changes to their firewall in order whitelist a new app.

Video

Watch a video demonstration of this use case. You can change the language for the video by selecting the Language icon in the upper right corner.

Typical Issue Life Cycle

  1. An internal IT team member completes a Change Request form from a JSM help desk that is only exposed to the IT team. 

  2. Since the change type is Standard and an SOP was selected on the change request form, the issue is automatically transitioned to AWAITING IMPLEMENTATION. 

  3. When ready, the Change Manager changes the issue status to IMPLEMENTING and work begins.

  4. Upon completion, a team member transitions the issue to POST IMPLEMENTATION REVEIW.  A Post Implementation Review form is automatically added to the issue. 

  5. The Change Manager sees that the change has been completed successfully, fills out the form and changes the issue to CLOSED. 

tip/resting Created with Sketch.

Set Up

  1. This use case presumes that there are a series of pre-approved Standard Operating Procedures for standard changes.

  2. Use Jira Automation to automatically transition the issue to AWAITING IMPLEMENTATION for standard changes with an SOP selected.

  3. Use ProForma automation to add an Implementation Review form when the issue is transitioned to the POST IMPLEMENTATION REVIEW status.



Workflow

Forms

Change Request

This form is available in the ProForma templates side bar.

Post Implementation Review

This form is available in the ProForma templates side bar.



Last modified on Jun 18, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.