Update October 2024: The information in this thread is no longer correct.
We just had an app update that changed the base URL (preparing for data residency, we switch to subdomains like de.*, us.* to reflect the availability zones). At the same time we switched our backend infrastructure. We had a solid plan on how and when to migrate customer data etc.
But the behavior we saw was nothing like people experienced according to this thread, making our careful plans quite obsolete. So you don’t fall in the same pitfall, here’s what we experienced in October 2024:
- We created a new version via the marketplace, pointing to the new descriptor URL with the new base URL. Testing in private, everything worked as expected.
- When we tried switching this new private version to public, this triggered a manual app review ticket. It took 8 days for somebody to approve the new app version.
- We expected the update to silently roll out. But although this is a minor version update (1.1.16 → 1.1.20), it has to be manually approved by admins in the UPM.
So, changing the base URL of your app, even just the subdomain, is a long process with a lot of gotchas. Switching the base URL between releases, as described by @ademoss in 2019, no longer seems to be viable. (Or did we miss something?)
I’d expect to have a clear documentation about that process from Atlassian. @hari, can you point us to where we can learn about that or put it on Atlassians todo list?