First Time Using Upgrade Plan Help

[frank121]

Hello, we are upgrading to Vancouver and this is the first year we want to utilize upgrade plan. I watched the toolbox video and I still have a question. 

1. If we have a 3 Stack Dev - TEST - PROD how would it work if we upgrade DEV/TEST together? The way I understand it is you need to publish an upgrade plan BEFORE upgrade. Im upgrading DEV/TEST together so how do i get the updates from DEV to TEST once im done with my skipped updates? Can i consume the upgrade plan after I have upgraded already? I upgrade DEV/TEST together because we have our process owners do testing in TEST and our developers work on any issues in DEV. We still need time to look at the skipped updates BUT need TEST upgraded so our process owners can test. 
2. Can we add update sets to our upgrade plan? If a process owners defines a problem due to upgrade we want to fix it with an update set. Can we include that update set to plan or do those fixes need to be manually imported?

[mfhaciahmetoglu]

It has been a while but as far as I remember, I opened it in a new window and using multi-select I moved them to the right destination. 

[Kristin J]

Morning! By opening it in a new window, do you mean the upgrade plan, and then you were able to move the records to their original scope?

We've been through a couple rounds of upgrade plan now and are going to Washington over the next couple weeks. I'm a little worried about our flows, and the whole scope thing with upgrade plan is driving me crazy. I feel like I'm in too deep now to get out!

I went to edit something on our itsm mobile agent the other day,  and was getting a "you're in ITSM mobile scope but this record is in upgrade plan scope" kind of message. As I dug deeper, some of the screens etc. were still in mobile agent.  SN Support said this was expected, but I don't know how complicated that is going to be when trying to configure/develop in multi-scopes within one product?! 😨

[mfhaciahmetoglu]

Morning! By opening it in a new window, do you mean the upgrade plan, and then you were able to move the records to their original scope? --> Yes!

Hope it helps.

[Adam43]

is it basically everything in the upgrade plan would return to 'global' then?

I'm looking at all the upgrade plan items and they make me think I should be evaluating what application they came from originally- ie.- this Jira Spoke record I should be trying to find a Jira application to move it to, but Global and the upgrade plan apps are the only choices- just checking before I make the move.

Also- would this have been something I should have done BEFORE I installed the plan on the target and upgraded?  or can these records be fixed after the upgrade happens on target instance?  As I type this, I think I know my answer..... 😞

[Adam43]

ok- I figured out- I can do the fix everywhere but Prod.  anyone know why I can't 'move to application' to move these records back to Global in Production?  specifically I'm trying on our portal config record now that I know that's the fix I want.  Last ditch, I'll do it in a sub, capture the change in a regular update set and move it up during what we call a 'technical release'.