Nah, let's wait for it to turn 18, at least we could have a beer with it. 

Haha best Ticket ever. I will throw a 10 year anniversary party at my office. Anyone wanna join?  

10 years and no progress

This is one of the most ridiculous blocks I've seen for such a product. We also will be looking for other means and potentially moving out of their cloud service which seems to be a giant money grab compared to on prem which is WAY easier to manage as well as doesn't charge you per person because they "may" have access to a project... ouch.

Is there any update on this feature request? When will custom subdomains for Jira SD be implemented?

There's still datacenter for onprem. Which means Atlassian is continuing to give the big FU-WeDontCare to people who are paying $42k+ a year for software.

That's half a developer salary... they can't take 10-20 hours to develop custom domains? Come on...

Hi,

you are partially right, David, but there is so much functionality missing in cloud versions that this sounds more like wishful thinking. In any case I believe we should give Atlassian some feedback and this is one of the places to do so. We are extremely disappointed with their approach and will move somewhere else after they transition to cloud and EOL server edition. If they don't want our money, we will just spend it somewhere else, c'est la vie.

Martin

such an obvious disregard for customer needs is quite eloquent. nice job atlassian.

This is such a simple feature to implement that I can't understand why they would frustrate people by not doing it.

I have got around the problem by using IIS and ARR which means everyone is sent to my IIS server by and nice, easy to remember URL instead of directly Jira and I just reroute the requests. Not something I should have to maintain separately though!

Just add this, such a small but important thing that is also the second most voted request.

For the nearest future we've decided to prioritise other areas of the Jira Service Management roadmap.

We hope that you appreciate our candid and transparent communication. 

The candid communication is appreciated however, the feature requested here seems to have a long history of strong community support and represents ongoing need of your Service Management clients. I'm hopeful that you will reconsider deprioritizing this request.

Is there any intention from Atlassian to include this in the development planning for Jira Service Management (formely Jira Service Desk) in the near future?

After a year of nothing from this we moved ourselves and others off JSD as this is critical and a big failure on their part to not get this in ASAP especially when it got voted to the top so fast.

In a few years we'll all be like, "Remember that company Atlassian?  Whatever happened to them?"  This is what happened.

Atlassian will soon be a history at our and customers' businesses as this is unacceptable to wait years for critical issues to be resolved when they're focusing on and prioritising riddiculous things such UI refresh that no one really needs. You're literally killing your own products - good luck with sustaining your corpo in future when customers finally give up on you and switch over to alternatives!

Hahaha, yes as Matthias before me wrote: this is cleary a big joke.

I received an Webinar invitation this morning "Free Webinar: Learn about Atlassian's Jira Service Management" 

The first sentence says: "Want to learn more about Jira Service Management in 2021? Don't miss out on this free 20-minute webinar session about"

Nope we don't want to learn about all that stuff which is fancy and coming this year if some basic functionality still doesn't exist.

At the moment I believe Atlassian made poor software architecture choices and it is just not possible for them to build such an feature. Maybe we get it on the Cloud Service ?

This is nothing else but a big joke.

The alternatives are not even close to any decent solution. For years this topic is been ignored and put aside. What needs to happen that this request finally gets the attention and execution it deserves?

@cmarriott are you are just shitting on your customer! This is one of the oldest and highest voted issues!

I am very disappointed  as this is one of key-point of acceptance. We use JSM for some business-teams. But our IT-Team decided against JSM. This is one of the reasons.

Raised 6 years ago, reviewed 2.5 years ago. Could we please have an update on this? Thanks

When will anything happen on this?

I believe this needs to be re-evaluated.  From an Enterprise perspective we want to provide a cleaner look and add more credibility to the links provided to customers, and internal users so they can be sure that they are accessing an acceptable site.

+1

Same issue as the comment above! Wrong URL shown to customers. Non professional look. 

Hope this will be implemented as soon as possible!

Please implement this. Apache reverse proxy only lets us enter a custom URL. The URL still resolves to the long original URL. This is confusing to our customers.

+1

Very Disappointing, lack of response to customer's feedback on an important feature. 

Six years of "gathering interest"... and still no solution for this around.

We are looking into writing our own "Service Desk", like @jan hein did...

Easy way to lose money, Atlassian!

Agree with pretty much all of the comments above; this should be part of the basic 'out of the box' functionality for a servicedesk product.

Atlassian - Please listen to your customers.

We've stopped working with Support desk from Jira and build our own. We built a simple ticketing system and  base added a fancy knowledge base. Integrated the ticketsystem Hubspot Service Desk for email support (and chatbot). All took 4 weeks.

Maybe it's time to change this stuff Atlassian.

BUELLER, BUELLER?! ANYONE?!

Atlassian... Could you please reply the quesitons?

looks to be linked to https://jira.atlassian.com/browse/CLOUD-6999 for the custom domain names.

Either way round, is there any update that could relate to this update?
https://blog.developer.atlassian.com/ecosystem-support-for-custom-domains/

Dont get it... embarassing for Atlassian

Very Disappointing, and very easy to implement.

Sad to see Atlassian not addressing such as basic need.

This is the highest voted non-closed issue, and the status is 'gathering interest'?!

https://jira.atlassian.com/browse/JSDSERVER-513?jql=project%20%3D%20JSDSERVER%20and%20status%20!%3D%20Closed%20ORDER%20BY%20votes%20DESC%2C%20updated%20DESC

It is a very basic requirement that would be expected from the beginning, a simple cname support link.

It is needed to fill a glaring feature gap between competitors like zendesk which of course does it.

It is a trivial feature to implement for atlassian, provide a subdomain to the support portal.

For those who are looking for a solution: UseResponse did pretty well in the last few years. Their solution is a public forum, a helpdesk panel, a knowledge base and also a live chat solution all-in-one and they developed some quite nice features here – and multilingual / multi-domain is basic standard there. Actually we're checking out if a migration from Jira ServiceDesk to UseResponse could solve our problem here. And, of course, it includes a plugin for Jira / Confluence integration, so backend developement could stay in Jira, while User-Frontend is handled by UseResponse.

Come on Atlassian team. This feature is not just about what customers are voting. It is about Atlassian prestige. I think that not all of your customers have the knowledge and skills to even implement a solution on masking servide desk url, but for those of us who really care about the best way and best practices to do things this is a very very important matter. Here at my company we have been customers for about 10 years now, we like your software, we like your solutions. They are great solutions, please, please solve this issue.

This should be an easy change to Jira to enable this and can't believe it's not included in the product.

Currently I'm having to get around this by using IIS on another webserver and using URL Rewriting to perform this, but I shouldn't really have to use a second web server to overcome such a simple task......

This is a big issue. Jira you need to figure out a way to allow this process so that we can redirect our old easy to remember support URL to your URL. 

Any updates?

One year futher (after many!)  and  what have the Jira (service desk) customers learned? Go to another software solution if need a proper subdmain for your helpdesk(s).

Still no update after May 9th 2018 where Atlassian said it wasn't on a their long term roadmap?

any solution to this issue? friendly url or rewrite? so i can use customer.domain.com for Jira service desk on cloud

Hi,

Any updates on this? 

Please help us connect a domain!

Yes indeed, did not manage to do it with a rewrite or proxy because of the internal requests..

Basic need.

would be great with the release of Jira 8 and JSD 4 to hear more about the timeline for this basic functionality...    

@3qml-sanc 

Does your solution address the jira-side issue of generated links back to the support portal?  Sure we can set up a reverse proxy to point foo.bar.com to our Jira ServiceDesk Project 27... but when links are send out to respond to the issue, all the links point back to the main Jira Site, and our aforementioned Service Desk Project 27, which in reality doesn't solve anything at all.

The goal is a complete and independent subdomain that's specifically for the particular service desk in question 

Hi @Michael: +1 Could you please share how you resolved the base url issue ?

Hello, we are still in evaluation phase, however this feature is as many say - must have. Our current work-around is using Refined Theme for Jira Service Desk. But only helps with parts of our needs.

Hi @Francis, hi @Michael:  +1 from our side. Michael – what have you done? Would be great if you could share a/your solution with us.

Hi @michael,

Can you share your approach of this setup?  I'm curious how you resolve the base url issue

Francis

Atlassian seems to ignore many important requests, delaying them for years, which is immensely frustrating.

But we've stayed with JSD, moving all company departments to it, in spite of the limitations.  On server, we've also managed to implement support.ourdomain.com and kb.ourdomain.com without too much trouble.

Any product you select will have it's pros and cons, we have decided that the pros outweigh the cons.

We rolled out JSD to 2 of our customers then found out about all outstanding critical unresolved for years issues hence decided to give up on it / looking for alternatives.

I assume at this point that most people have just given up on JSD. I know we have.

I don't think Atlassian "get it" that information security is an issue for many of it's customers (actually all of it's customers but the rest don't yet realise it). I suspect this is because they live in an Agile bubble where everyone trusts each other. We will either have to use a different product that does include sub-domains and get a Jira connector, or hack something ugly ourselves.

Yep, I got a reply to my rant about how bad it is stating Atlassian is taking every feedback very seriously etc. but facts are the opposite. It's a great system but we're simply being ignored and marketing profit making ideas are prioritised AKA "sell and ignore/forget".