Why is it <domain>.atlassian.net and not <domain>.jira.com? Wouldn't the latter make more sense?

Alex Pilafian March 1, 2016

At skunktime (skunktime.atlassian.net) we would just prefer if we were able to use skunktime.jira.com, and we recognize that this would be the more intuitive thing since we're trying to get to our cloud-based JIRA installation. Can you guys make that happen? Don't you agree that it would be better? Little details matter when your clientele are computer programmers.

2 answers

1 vote
Robert Massaioli _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 1, 2016

Unfortunately Atlassian only offers atlassian.net domains at the moment. You should make this request on the issue linked to this page: https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html

0 votes
johnrote
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 20, 2016

Another reason may be that many of our products integrate together nicely and can use the same atlassian.net domain.  So, if you used both JIRA and Confluence, you'd just have one .atlassian.net domain that would allow you to log into both products from one place rather than having one .JIRA.com domain and another .confluence.com domain.   

Our product management team may have additional/clearer insight to provide, but I believe that allowing multiple integrated products to log-in at the same domain may be part of the rationale.  

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events