What is an RFC ticket?
Why is it important?
How to complete an RFC ticket in Service Manager
Navigate to tab ‘Change Open Prompt’.
Fill out ‘Change ID’ and ‘Phase’ fields.
Initiator
Fill in fields with details of the team member who will coordinate the release.
Change Detail
Navigate to tab ‘Change Detail’ to the left-hand side of the ‘Change Open Prompt’ tab.
Fill out the following fields:
‘Category’ - Software
‘Impact’ - 4 - User
‘Urgency’ - {2 - High}
‘Risk Assessment’ - {4 - High Risk}
‘Planned Start’ - {prod release start date}
‘Planned End’ - {prod release end date}
Impact / Justification
Navigate to tab ‘Impact / Justification’ to the left-hand side of the ‘Change Open Prompt’ tab.
Fill out the ‘Impact Statement’ field, and include the following details:
Number of hours system will be unavailable to users - {30 hours}
Indicate why the system will be down - {The system will be down up to 30 hours while the software and databases are updated}
Fill out the ‘Justification’ field, and include the following details:
Indicate what will be included in the release - {RSIG production; ROFs / RSIG integration enhancements and bug fixes}
Project manager contact - {Project Manager / Contact Rivers, William <william.rivers@tc.gc.ca>}
Team lead contact - {Alburger, David <Alburger.David@tc.gc.ca>}
Backout Method
Navigate to tab ‘Backout Method’ to the left-hand side of the ‘Change Open Prompt’ tab.
Fill out the field, and include the following details:
Statement indicating that a backout or rollback procedure is in place - {We have a documented roll back procedure for backing out of this change. We will put this document in the deployment folder (RDIMS#: 8964742)
Outline rollback procedures -
{Microsoft Click Once