nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Did I misconfigure my Jira URL? Wondering why Jira isn’t at `/jira` like Confluence is at `/wiki`

Melisa K_ Savich

Hi everyone,

I originally set up Jira Software and Jira Service Management for my organization, and both have always lived at the root URL:

`https://[my-org].atlassian.net`

Recently, we added Confluence to the same Atlassian site, and I noticed its URL is:

`https://[my-org].atlassian.net/wiki`

That got me thinking—did I make a mistake when first setting up Jira? I would’ve expected something like:

`https://[my-org].atlassian.net/jira` for Jira Software
`https://[my-org].atlassian.net/jsm` for Jira Service Management

Instead, both Jira products share the root domain, with no subpath like Confluence does. There’s nothing functionally wrong, but I want to understand:

Is this URL structure normal and intentional for Jira Cloud products?
Should I have taken a different setup approach if I wanted cleaner or more segmented URLs?
Does the `/wiki` path for Confluence indicate a best practice that I somehow skipped when setting up Jira?

I’m just looking to confirm whether I followed the standard Jira Cloud conventions or if there’s something I should revisit or reconfigure.

Thanks in advance for any clarity!

Accepted answers

Evgenii

Hi, @Melisa K_ Savich

You can't really misconfigure anything — Atlassian controls the structure.
The URL is basically exactly as you wrote: <a href="https://your-company.atlassian.net/jira/" target="_blank" rel="nofollow noopener noreferrer">https://your-company.atlassian.net/jira/</a>

However, in some areas like the admin interface, the /jira/ part may not show up in the address

All comments

Evgenii

Hi, @Melisa K_ Savich

However, in some areas like the admin interface, the /jira/ part may not show up in the address

Melisa K_ Savich

Thanks, @Evgenii — that helps a lot!

Out of curiosity, are there any cases (now or in the past) where an organization might want a product like Jira to live on a separate subdomain, like jira.<org>.atlassian.net instead of everything sharing the root domain?

I’m wondering if that kind of structure has ever been available for enterprise setups or if it’s something Atlassian’s considered. It would make sense for larger orgs that want clearer product separation (e.g., support.<org>.atlassian.net for JSM vs. jira.<org>.atlassian.net for internal project tracking).