Last year, we published a blog regarding the development of our new site rename feature, including information on the impact of this feature on your Cloud apps.
The feature allows customers to rename their site from foo.atlassian.net to bar.atlassian.net. Since April, this feature has been available to customers via submitting a Support request. We action a site rename request based on the criteria that the ecosystem apps installed on a customer’s site are compatible with our feature
Over the past few months, we have been reaching out to vendors to verify the compatibility of their apps with our feature. This is an ongoing process and we have listed vendors who have confirmed with us on this public ticket here (CLOUD-10809 – Ecosystem vendors that are compatible with the Cloud Site Rename feature ). If you want to verify your apps’ compatibility with us, want to test the feature on your site or have questions, please reach out to us via here.
We are actively developing a self-serve option for customers and the site rename feature is expected to be available to customers via the Admin UI in the near future.
Concurrently, we are working on enabling customers to have custom domains. The custom domains feature enables customers to configure their Atlassian products to be accessible via a custom domain e.g. the customer can change the site URL from foo.atlassian.net to jira.foo.com. We’ll be engaging with vendors soon on the impact of this work.