Upgrade monitor skipped records after patch update

[pauladams]

Hello,

We have recently updated our development instance with patch Istanbul patch 10 C. I've looked at the upgrade monitor and have few questions for you experts:

1) After the upgrade, we have been testing the functionality we had before the patch and everything is working as expected. Do I still need to review the skipped updates and take action on them?

2) What does the priority of the skipped record indicate? Majority of the skipped records are Priority 5, few are 2, and a very few are 3 and 4. Does priority 5 mean take it easy and just ignore?

3) Do we need to repeat this exercise of reviewing the skipped records in all the environments as our Dev, UAT, Staging and Production instances are identical and it is likely to skip the same records in all the environments or can I capture the reviews in an update set and promote to the other instances?

4) If the reviews can be captured in an update set and can be moved to other environments, do I need to move the update set prior to the upgrade of the target instance?

5) Finally, what happens if I just leave them without reviewing?

Thanks

Pa

[Nia McCash]

Usually, configs are reverted when we no longer need our customizations and want to take advantage of out-of-box (OOB) configs.  I believe if I were to revert them via update set, they would still be considered "customized" because I was the last to update the record even if the code is exactly the same as it is OOB.  So on the next upgrade, ServiceNow would mark this record as skipped again and I'd have to review it again.