To create a change or to review existing changes, see ITS Change Management.
...
Complete the form. All RFCs that alter production configurations or programs need to have been tested in a non-production environment and include documented procedures to regress the change via a set of well-understood back-out procedures.
If this is not possible, the Functional Approver must indicate the reason why such practices are bypassed.
The Approvers field is for your Team Lead. While approval is not required for Expedite Changes, adding your Team Lead will allow them to receive notifications for the ticket. To enter the Team Lead, enter their email address or lastname, firstname.
Additional technicians are any technicians who will be working on or must remain updated about the change order. To enter the additional technicians enter their email address or lastname, firstname. They will be added as Watchers to the ticket.
At the bottom of the form, you can choose to publish a notice on the IT Status page.
Choose Yes from the dropdown for Post to IT Status.
Enter a brief description of the change. This description will be displayed when a site visitor clicks on the link for the change.
When you are writing a message for the IT Status page,
Keep it concise and focused.
Identify the issue, who it impacts, and how it affects them.
For the Services Impacted field, select the appropriate service. If multiple services are affected, you can select each affected service. To do so,
Hit Ctrl + click (for Windows) or Command + click (for macOS).
If the service is not listed, choose Other.
Enter the service in the Service Impacted (Other) field below.
Click Create to complete the request.
...
You can reach out to the following individuals for questions pertaining to this document:
Sherry RodriguezKeith Parks, Change Manager, Service Management
(860) 486 -02956676
Email: sherry.rodriguez@uconnkeith@uconn.edu
Andre Corsini
(860) 486-3372
Email: andre.corsini@uconn.edu
...