What about the original request a *custom* domain? Which means *any* domain being a CNAME of acme.atlassian.net should work.
And/or an easy way to attach a reverse proxy (CDN with rewrite) for using acme.com/jira
Maybe you can explain to us, what you had in mind when designing this with 2 levels of subdomains and having a fixed list of 1st level subdomain names? But i think it doesn't matter, when reading the previous comments ... it is just hard to understand what's the problem here, when having so clearly defined user request.
@Luke Liu - two levels of subdomains is a little overkill, and not a typical usage pattern for those using SaaS tools. Hoping this is just an initial phase to support custom domains?
Our company is stuck in migrating because the lack of custom subdomains. Our needs are super simple. We want to have Jira and Confluence in cloud, but under our domain:
We are desperate too, by the forced moved out of our confluence on prem server, but at the same time basic features are preventing use to move to the cloud version. AsCLOUD-6999 is identified for years/decades, what should we tell to our IT management? to our business manager? That's crazy.
is this move early enough to give us the time to move from OnPrem to Cloud before Feb 2024? Probably not for each non trivial implementation of Confluence.
(unfortunately the same applies for JIRA/JIRA Service Management)
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mandatory second subdomain is superfluous and harmful to adoption. Repetition is the way to get your internal customers remembering tools - focusing their brains on using the tools instead of trying to remember something that is very foreign (second subdomain).
Quick and frictionless user adoption is the key to product success. If I have a large group of folks who have been JIRA resistant/ignorant - you want the url to become part of their vocabulary, you want them to be advocates and champions... and even though it seems silly, a second subdomain isn't common parlance in any successful product. Imagine if you needed to remember: my.bankingaccount.wellsfargo.com or file.share.dropbox.com - its extra mental baggage folks won't understand and only defeats simple adoption of the product.
Optional secondary domain for those who see value is perfectly fine, mandating it will alienate our internal customers who already have an impossible time remembering company.atlassian.net.
p.s. Yes, some folks use bookmarks, and some folks use Okta tiles, but that doesn't encapsulate every scenario we face in IT. Lets make it easy to remember how to get to our very useful tools instead of creating unnecessary friction.
Putting this article together should have felt embarrassing. It makes no sense how no one in the development team responsible for this was able to speak up and say what a dumb idea this is.
The very websites we use to discuss this are jira.atlassian.com and community.atlassian.com
I have been following this ticket for a few years and feel like I should've seen this coming. A few years ago it was delay because custom domains are "hard to implement"
Extremely disappointing for a company that builds tools to help developers.
I bet the person responsible for this implementation is the same person that was responsible for the original Jira that was so bad, companies around the world needed to hire full time Jira administrators just to manage permissions.
@Luke Liu - I hope you and your team are monitoring this thread - would love to hear your thoughts on the feedback so far, and curious if you have an update since your last comment (mid-March).
I know your job isn't easy, we definitely appreciate your efforts in all of this! 🙌
@Michael Ziegler I don't think anyone here wants 2 levels of subdomains... but so far it appears to be the only option that Atlassian has provided.
I've been doing this a very long time and the only time I recall seeing multiple subdomains used (other than when forced into it) are universities and the government.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
I am just afraid that it took over a decade to come to this solution and that it will take another decade to determine that the solution is actually what everyone here is simply asking for of subdomain.ourdomain.com.
Just how hard is it to do this. I worked on military systems that were easier to change then this and we had to deal with the Pentagon and Politicians.
@Michael Ziegler If judging by this discussion thread, and CLOUD-6999, is anything to go by, then the results will be pretty obvious.
Atlassian's lack of engagement in this thread could also suggest that they're figuring out how to handle this backlash as well, and perhaps it's back to the drawing board.
The 'keyword' 1st-level subdomain requirement must be due to some architectural limitation of Atlassian Cloud that hasn't been divulged to us. It would also be helpful if Atlassian also divulged what these 'keywords' actually are, so that we can determine how fit for purpose they are too.
The following image is from your Cloud Roadmap. We all are waiting to see if Atlassian will keep the promise or will use a workaround for the conceptual/architecture issues and tries to force the third level domain. We like JSM and the insight Asset Management but if Atlassian forces us to use the third level domain we will go to another vendor instead of launching on Atlassian Cloud.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
All you who say that xyz.domain.com is what you want, please rethink. We don't want them to have anything to do with how we name our URLs at all. Subdomains are irrelevant. https://domain.com should be as valid as https://xyz.domain.com. As should https://xyz,zyx,domain.com or whatever. Period.
91 comments