For older, upgraded instances, if your Update Set Picker is not automatically updating its list of available Update Sets when you create a new one or close an existing one, the problem is with the "ui_update_set_picker" UI Macro. Older instances, going back as far as Berlin, may not be upgraded properly, because, in order to hide the picker in your Production instance, you must set the Active flag to false and that means a change to the record. That change marks it a custom record now and no longer upgradeable. That record will always be viewed as a custom record each time you clone back to development, so will always get skipped on upgrades.

In order to fix it, you will want to revert the record to OOB in your production instance so it will be pushed down to dev during the next clone cycle. To do this, select "Upgrade History" from the "System Diagnostics" application and find the latest upgrade you've performed and load the record:

Filter the "Upgrade Details" related list to show "File name = sys_ui_macro_49a50b9ca9fe3dba0059d0f944e412d1":

You should end up with 1 record showing in the list with a "Disposition" of "Skipped". Open that record and click on the "Revert to Out-of-box" button. This will upgrade the UI Macro to the latest version. That will fix your production instance.

In order to temporarily (until the next clone) fix your development instance, where it really matters, first export the UI Macro record from the production instance as an XML file. Then, select the "Default" Update Set in development and import that new XML file. Now you have the latest file in development as well as production.

When you now turn the UI Macro on (in development) and off (in production), that change is no longer considered a custom change, so you will still get automatic updates to the macro. This is because of a feature that was added way back in Calgary - Administering Update Sets - ServiceNow Wiki