Can I rename my Atlassian Cloud site URL?

Question

Hi everyone,

We're a small startup (~10 people) that recently rebranded our main product from JunctionNet to Cargonaut. Our Atlassian Cloud site is still at junctionnet.atlassian.net and we need to update it to cargonaut.atlassian.net.

We've already updated the site display name and logo, but the URL still shows the old brand which is a problem because a Cargonaut investor is now funding our Atlassian subscription and the old URL creates confusion in investor-facing links and communications...

I've already updated site display name and avatar in Admin Console, but I can't change the URL. Has anyone successfully gotten their site URL changed by Atlassian? If not, any creative workarounds I'm not thinking of? (Custom domain, redirect, etc.)

We have active sprints, existing ticket history, and CI/CD integrations tied to JNET issue keys, so I want to minimize disruption.

Any advice appreciated!

Thanks,
Ana

Germán Morales · Answer

Hi @ana_lugo, welcome to the Community. @Arkadiusz Wroblewski already covered the core path well, so let me add a few things specific to your rebranding case that often catch teams by surprise.

The subdomain change happens at admin.atlassian.com under Products (or Apps in the newer UI) > Product URLs, performed by an Organization admin. Requires Standard, Premium, or Enterprise on at least one product in that site. A few things worth knowing before you pull the trigger:

* You can only change the URL three times per site. If your org has already changed it a few times in the past, the Update button will be greyed out.
* The old URL gets locked. Atlassian reserves it indefinitely so no other tenant can claim junctionnet.atlassian.net, and the browser redirect from the old URL to the new one is on by default.
* Issue keys are not coupled to the site URL. Your JNET-123 keys come from the project key, which is a separate setting at Project settings > Details > Key. If you also want to rebrand them to CGRT-123, you change the project key there, but be aware it triggers the same kind of integration breakage at scale (any webhook subscription or CI rule that hardcodes the key needs to be updated).
* Custom domains are an alternative if you want a fully branded URL like jira.cargonaut.com instead of cargonaut.atlassian.net. They require Premium (Jira or Confluence) or JSM Standard, and you set them up in Settings > Domains in admin.atlassian.com.

On the CI/CD side, the redirect handles browser traffic but not API clients: any integration calling junctionnet.atlassian.net/rest/api/... needs the base URL swapped. Webhooks registered against the old hostname need to be re-registered against the new one as well. Worth running a grep across your IaC and CI configs before you do the cutover.

Official doc with the full procedure and limits: Update your app and site URL.

Hope this helps.

Arkadiusz Wroblewski · Answer

@Trudy P Claspill

Never used this form, so good to know! 😂 You're really our Forum Queen! 👑

I specialize in answering questions, not asking 😅

Then that topic is also for a Feedback Page (you know which one I talking About), because with an event happening later this year, we need to have more details in this form. This can save us time asking for so many details.

Trudy P Claspill · Answer

@Arkadiusz Wroblewski

Just FYI - the options available to a Question author for specifying their level of access is just a checkbox for Admin which shows "Product Admin" when checked.

There is not an option to specify the type of admin role; Organization vs Site vs Billing vs. User Access vs. Product.