When migrating from Jira Server to Cloud do App plugin keys remain the same in WFs?

[Mike Rathwell]

I am planning a potential move from Server to Cloud for... reasons... I've done the analysis on what plugins and the like are/aren't supported and what my workarounds might be for the ones that aren't. Mostly it involves dumping the system and grepping the giant XML file for the App key to find the WFs they are in and doing it another way.

I have done that before for an app that wasn't being upgraded and holding a version upgrade. I rooted it out and did it another way. Painful but doable. Two days later, they released an update. Grr.

So... my question is: If I do all this work and then move the data over to the cloudy version, will all the app keys that have a mated pair between server and cloud remain the same or will I need to root through the XML again to update from server app keys to cloud app keys?

[Brant Schroeder · Accepted solution]

The platforms are different.  I believe for all products as well as apps you will need to work with the vendor to see if you can get a credit applied to your cloud licensing costs. 

[Mike Rathwell]

Hi @Brant Schroeder ,

I was actually talking about the plugin keys as they would appear in WFs and the like, not the actual license keys. I've identified all the plugins I have to eradicate BUT what I wonder is, when I import Workflows and the like, will the app keys be the same and the workflows work?

For example, on my hosted server instance, Adaptavist Scriptrunner is "com.onresolve.jira.groovy.groovyrunner". Will it still be the same when I migrate to the cloud?

So... basically, what I am wondering is that I go to the work of re-doing workflows to use only plugins that are available in the cloud.... will everything work when I move it there?

[Brant Schroeder]

As you migrate workflows that contain plugins if the plugin migrates it should work in cloud.   Sometimes when you export workflows it will let you know that a plugin will not export and you will have to recreate those steps.

[Mike Rathwell]

Thanks @Brant Schroeder ,

That was exactly the answer I was hoping for. Part of my migration process will be to weed the ones that aren't supported before I try to migrate to make it as smooth as possible.

I really am not looking forward to trolling through that giant XML file for various app-keys...