Updating an Atlassian Product URL

Joe Hutchings
Oct 1, 2021 11:45:33 AM

TEAM IM uses Atlassian products including Jira Software, Jira Service Management, and Confluence to manage our portfolio of products and customer-facing services. Atlassian recently announced a much anticipated new capability for customers with Standard, Premium, or Enterprise plans to update their product URLs. In line with our rebranding efforts to TEAM IM, we wanted to take advantage of the new feature to change our access URL from teamanz.atlassian.net to teamim.atlassian.net.

The update process is simple, straightforward, and takes only minutes to implement: https://support.atlassian.com/organization-administration/docs/update-a-product-url/.

To update a product URL:

  1. From your organization at admin.atlassian.com, click Products > Product URLs.
  2. From the site where you want to change the URL, click Update URL.
  3. From the Update URL dialog, enter the beginning of the new site URL. Enter at least 3 characters. You can use lowercase letters, numbers, and hyphens if they’re in the middle of the name.
  4. Click Continue.
  5. From the Updating product URLs dialog, you’ll see a list of products that are updated with the new URL. Click Update to confirm you want to change the URLs.

Atlassian Update URL Dialog Box

Note: It may take up to 5 minutes for the change to take place.

Atlassian is quick to point out when you update a site’s URL. They preserve the previous URL in your site’s history and it isn’t released for use on another site. If someone visits the previous URL from a bookmark or link in an email, it still works and Atlassian redirects them to the new URL. This is great news for customers and also meant integrations with Atlassian products such as single sign-on continued working seamlessly after the change. TEAM IM also received confirmation from Atlassian Support that email addresses for Service Management sites are preserved in a similar fashion as aliases after the URL change meaning customers could continue using old email addresses.

While it took a little planning and communication to deploy the change, it was nice to be able to quickly take advantage of new functionality without imposing any negative impact on internal users or customers!

No Comments Yet

Let us know what you think