Summary
This release primarily involves:
Progression
Status |
Activity |
Description |
Duration |
|---|---|---|---|
|
Identify release date |
see Release Calendar |
minutes |
|
Schedule cloning |
clone from prd to: pre, trn, and tst for after release; https://hi.service-now.com/ |
minutes |
|
Schedule code review |
this should happen after initial handover and before release |
minutes |
|
Submit change request |
Open a build/test change request in https://yale.service-now.com/, assign to |
minutes |
|
Start release document |
Copy from template ServiceNow Release YYYY-MM-DD |
minutes |
|
Requirements freeze |
Curate, then freeze requirements, providing estimates for each using estimator spreadsheet or equivalent |
hours |
|
Build phase work |
Begin work in dev |
days |
|
Unit tests |
Ensure all pushed to tst & unit tested |
hours |
|
Initial code freeze |
Hand over initial requirements list for functional & QA validation in tst |
minutes |
|
Conduct code review |
Shouldn't take long, just basic validation of approach and docs |
hours |
|
Defect fixes |
Iterative follow-up work in dev, test for defect resolution |
days |
|
Finalize release |
Identify changes & updates that are going/not going. Push to pre. |
hours |
|
Final code freeze |
Hand over final requirements list for functional & QA validation, w/ regression, in pre |
minutes |
|
Go/no-go |
Decide to push to production. |
minutes |
|
Production deployment |
Push to prd. |
hours |
|
Production rollback |
If applicable; follow ServiceNow Rollback Procedure. |
hours |
|
Notify stakeholders |
send out email w/ summary status & link to release documentation, close out RFC and cancel clone requests, if rollback or no-go. |
minutes |
|
Target/Actuals |
Deliver target/actuals using estimator spreadsheet or equivalent |
hours |
Change Control
Release Notes
https://yale.service-now.com/kb_view.do?sysparm_article=KB0000066
Documentation
Detail is provided in the description. Full implementation detail is captured in the update set, which can be viewed (with admin rights) by drilling down into the links.
Requirements/Defects
Requirement (Original Names) |
Functional Tested? |
QA Tested? |
Dev Status Notes |
Description |
|---|---|---|---|---|
Defect 403 |
|
|
|
There should be a Bomgar Sessions tab at the bottom of incidents. Reported by Lori Seluga and Bill West. Need more information on what this Bomgar Sessions tab should do so we can test its functionality to ensure it is working correctly when it is added into the Incident screen. |
Defect 406 |
|
|
|
The link in the Incident email resolution notification to contact on a itkcet is pointing to the Yale Test instance instead of the Prod instance. Note that I checked all other client facing Incident email notifications and this is the only one where the link is incorrect. Notification #4 (Notification ID: 4 - Incident Resolved): |
Defect 408 |
|
|
|
See INC0072373 for reference: The 'Your Incicent has been placed On Hold' email notification is addressed to Contact (Houle) AND Client (Prof. Gilmore). This results in client receiving confusing email that is addressed to Houle. Only Contact should receive notification email. |
Defect 409 |
|
|
|
See INC0072373 for reference. Initial email confirmation when ticket created (sent 2012-11-05 15:50:57) had incorrect salutation. Email was addressed as "Dear ," with no name. |
Approved Updates
Update Set (Original Names) |
Description |
|---|