Upgrade Plan in DEV instance causing issues with other Update Sets in Global

[Luiz Lucena]

Hello everyone, 

We have 3 instances, PRD, TEST and DEV.

In DEV, we enabled the Upgrade Plan in an attempt to help with future upgrades, but instead of helping, this is causing confusion with regular update sets in Global. 
We worked in something in DEV, captured in a update set, marked as completed, exported the XML and then imported into TEST instance, when previewing it said many records were in different scope id and we noticed was the scope id for that Global Customizations - Upgrade Plan.

How to avoid this?

[Luiz Lucena]

I think I understand now what happened. 
We clicked the button (in DEV) to create an Upgrade Plan, then we reviewed the skipped changes but never published the Upgrade Plan to an Update Set. 
We did that now and let's see how that goes with other update sets.

EDIT:
That didn't work, we still are seeing update sets being moved to upper instances and warning about different scopes because of that Upgrade Plan.

[mfhaciahmetoglu]

Hi Luiz, we also have encountered the same problem. Have you managed to resolve this issue?

[Nia McCash]

You can move all records back to the 'Global' scope by

1. Navigating to the “sys_app“ table and open the “Global Customizations - Upgrade Plan” record.
2. In the 'Application Files' related list, select the files that need to move to the global scope.
3. Click on “Actions on selected row” and select “Move to Application” from dropdown.
4. A pop-up will appear, on that select “Global” and click on “Move” button.

[Kristin J]

Hi Nia...I know this is an older post now, but have you had any repercussions from moving files from the Upgrade Plan scope back to Global? We have actually made a update sets in that "Global Customizations" scope just because we didn't know what to do, and it seemed to work. But it also seems weird to use that scope for new development/modifications?!

Thanks in advance for any info/comfort you can provide, lol,

Kristin