Perhaps I am missing the point, but you may agree that so does Atlassian. The existence of this case is not much of a relief to me, as my team needs to have a solution and not a 10 year old case as an excuse for not having one. It is unfortunate that I had to make the decision to cancel JSD, but it had to be done to solve the problem, not out of spite. I allow that my previous comment was driven by emotion, though.

So, while not a solution, I did find a workaround for my end users that at least allows them to connect to a single custom domain which ties into my SSO.  It does not change the site or the URL, but it helps with branding a little.

Since I use Cloudflare for my DNS & DDOS, I used a feature they have called "Page Rules" which allow a domain to host a CNAME in DNS + a 301/302 redirect rule as part of the DNS proxy service.  In this case, I was able to create a cname of "jira.domain.com" which point back to "domain.com".  Once that CNAME was created, I created a Cloudflare Page Rule which takes any DNS hit for "jira.domain.com" and does a 301 permanent redirect to:  domain.atlassian.com/home/.

I did the same for Confluence (wiki.domain.com > domain.atlassian.net/home/wiki/).  

Now my end users can at least remember my service/domain nomenclature that all of my other services use - but its still Jira and Confluence.

NOTE: I am not taking away from the fact that Atlassian should have prioritized this years ago and should be working to fix it now in short order.  It is an common solution that everyone else supports - and if they don't do it properly, they will lose a lot more than simple customers.

@Boris you are missing the point. Everybody on this thread since the last decade just uses this as an example to show to her/his own customers if they have some feature that is not really coming along for years. This discussion is not one of product, but one of relief.

I found a solution! Unsubscribed from JSD completely and moved my helpdesk to HubSpot... 

+99999

This is the one feature stopping me from utilising Jira. Even if the custom url/domain was available just for customer facing products like the service desk customer portal. I am not worried about the admin/agent facing products so much. I just need it easy for end users in our organisation to access the portal to log jobs.

+1

Created:08/Jul/2011 3:58 PM

don't you think it's time to finally release it?

So many people waiting for this feature, and it stops some people (like me) from moving to cloud.

I was a large enterprise customer running Jira Datacenter prior to moving to a new company and building a new tech strategy.  One of the first things I did was start evangelizing about Confluence and Jira, making plans to integrate it into our SSO stack and quickly started creating content in the cloud instance (we aren't large enough for Server) - only to find out that not only are custom domains not supported, they have been sitting on it for 9 years.

As organizations implement SSO for their company in a sprawling SaaS environment, one that is literally filled with multi-tenant products, using custom domains is not a nice-to-have but critical to running an effective IT org.  service.domain.com is how you train users to always remember how to log into services.  So now my portfolio looks like:  dropbox.domain.com, asana.domain.com, smartsheets.domain.com, lucidchart.domain.com, and domain.atlassian.net/wiki/home.

This is beyond disappointing, and it looks like their backlog of technical debt prevents them from doing something that every other multi-tenant SaaS service has already figured out and is now table stakes.

I hope this gets added in the near future. I can't imagine how large of an undertaking this is and I wish the teams luck finishing this. I can also not imagine how frustrating it must be to subscribe to this issue for years and not see much progress made. I've only been using JSD for a year and we like it quite a bit, but the enjoyment may have worn off if I'd been using it for 9 years waiting for this feature. Other tools like Zendesk or Service Now would start looking much more appealing.

There is no expected release date for custom domains? Maybe not for service desk but at least for cloud Jira instance?

20 teams working on this. Now we have already May. When is the release expected?

Very excited for this release! Thanks team

20 teams over the last nearly 3 months should be enough to build a wall for the US/Mexico border. I would of also assumed that during these covid-19 times that more time would be available if people don't waste it on online meetings.

It could be a good opportunity to re-write Jira in golang or would that take 40 years to do?

@ŞAHİN SÜLEYMANİYELİOĞLU,

Do not bank on this functionality to be available soon.  Even if the development has been completed or is near completion, I doubt if you are "ready to go" you will have this in time.

This is an improvement from Atlassian's end that is taking more time than we would all like to occur. 

@Vikash Kumar,

There was an announcement on how this will be implemented on 9 September 2019;

"From the product perspective, our main focus right now is to provide this capability for Jira Software Premium. This means, for example, we’re working towards enabling you to configure Jira, previously accessible on acme.atlassian.net/, to be accessible via issues.acme.com.

For Jira Service Desk customers, JSD’s customer portal will remain on the /servicedesk path in the first phase of this feature. If you have subscribed to Jira Software Premium and Jira Service Desk on the same site, it will be accessible via issues.acme.com/servicedesk."

So for your example, I would imagine you can have your plugin on myplugin.itsMyWebsite.com because that's your own subdomain with whatever you have running there.

It probably won't be jira.itsMyWebsite.com, it'll likely be jira.itsMyWebsite.com/servicedesk.

However, you could have your site running on subdomain of jira.itsMyWebsite.com to always redirect / add the /servicedesk. You likely won't be able to hide this /servicedesk part.

In terms of modifying the css/jquery - I'm not sure this is possible in the cloud version, but only the server or datacentre versions.  It does appear though, that custom domains is only going to be available on the Cloud edition (via the Jira Software Premium).

I also don't know if this will only work if you have both Software and Service Desk, or only Service Desk.  - too many unknowns at this stage.

Please note: my information above is based on assumptions - I do not work for Atlassian, and I am only going by what I have heard / seen / read / watched on this topic, mixed with some of my own experience using some of their products.

Does this also mean that I can have my Jira at jira.itsMyWebsite.com and also deploy my custom plugin on myplugin.itsMyWebsite.com. With that, will the cross-origin problem be solved as well? I will be able to modify Jira's UI with custom css/jquery as we do in the server plugins?

Hi,

Any development or progress on this one?

We've been testing Jira for 2 months and now ready to go but we can't use the system without a custom domain option due to internal (mostly marketing) policy reasons. And actually we are on a clock and I must go live very soon.

So some feedback about if it is ever gonna be possible or not is much appreciated.

Currently considering documentation options, and this might be a deal-breaker. 

I spent too much time following this request. I'm stopping watching and will switch the ecosystem of our team with the first opportunity available.

By the way, guys, are you aware of [Space from JetBrains|https://www.jetbrains.com/space/]?

I get that it's hard. I'm a software developer myself, and my company runs its own SaaS as well (with custom domains being available from day 1, mind you). However, come on. It took 7 years to land a man on the moon. Granted, it was one of the biggest projects of the biggest economy. But comparatively, is this feature really even more than Atlassian's moon landing?

"We choose to not implement custom domains for Cloud apps in this decade and not do the other things, not because they are hard, but because we simply can't." Then fast forward a decade for the historic words of "one small step for the internet but a giant leap for JIRA?"

Also, I'm here for the rants, not the feature. I mean, obviously.

I used to enthusiastically recommend Atlassian's products to people that I worked with. I haven't done that in years and I don't anticipate doing so again

This is me - used to fight tooth and nail to get off the vast array of other systems out there and onto Jira - but right now I have a long laundry list of bugs (github integration, broken again this week - even though this is the "new improved connector")

They've made the UI less and less intuitive, they're incredibly slow moving on existing issues (user merge is still open too from memory), and to top it all off, now they want to charge me extra to see what permissions apply to a particular page I'm on?

Atlassian has lost my recommendation, which is a shame, as I grew up just down the road from them, so I always used to be so proud of them as a company representing Australia.

@Stuart Mills - I have spent the last 7 years as lead architect at a SaaS company responsible for the ongoing support and development of a web application which was originally created in 2005. Believe me, I am fully aware of how difficult it can be to change something at a fundamental level in an old sprawling code base. With that said, it has been nine years. NINE. This cannot be understated. They could have literally rewritten JIRA from the ground up in that time. Clearly, Atlassian had higher priorities during that period. That's fine. We understand. You have to do what you have to do. I have no doubt that they made a lot of money doing whatever it is that they've been doing during the last 9 years. However, what Atlassian needs to understand is that decisions have consequences. Ignoring their customers for nearly a decade has permanently damaged their reputation with me and, based on what I see in this thread, likely with many others as well. I used to enthusiastically recommend Atlassian's products to people that I worked with. I haven't done that in years and I don't anticipate doing so again. When people ask for my opinion, I tell them to use GitLab. It's not reasonable to expect that your customers are going to be happy with you after you spent the last decade ignoring them. Even assuming that they add this feature(I'll believe it when I see it) it will be too little too late. Atlassian is no longer the cool innovative company which believed that the product should sell itself. Atlassian is a lumbering behemoth with an army of UX engineers who are so far off the rails that I can never find the settings I'm looking for despite an inbox full of emails talking about how much easier the product is to use.

49b238e2b374 - Regardless of Refined's implementation - the fact that it's there, in their own store, demonstrates that not only do technical solutions exist - but they have done so for some time.

Is it the perfectly architected masterpiece they envision when they think "custom domains"? Perhaps not. It's also not 1 or 2 years later - it's 9 years later for functionality which is pretty fundamental for any whitelabel product.

They could have rolled their own, more fully featured version of Refined and then built and expanded upon that numerous times by now, but they didn't.

Instead, old leadership is off relaxing in simple dev shops while their stocks earn them $2m+/yr in dividends, and the people left are running what used to be a world-leading product into the ground.

Source: My tax agent sent me their old tax returns by mistake last year

> However, if you had any experience in a software development house offering customer-shared SaaS, you would understand the nuances of how applications are developed, and unfortunately how some applications are hard to introduce fundamental change to

I'm DevOps Lead Architect at a company that does exactly that. I get things can be hard, but there's hard and then there's 9 years hard. Just like when they took away the basic security functionality on Jira comments, rolled that out by default, and then spent 12 months telling us it was "coming soon" whilst it was already enabled in the very instance we were coming to complain in.

Seems most people are complaining.

• Yes, it's inconvenient it doesn't exist after 9 years
• Yes, it's inconvenient that the focus in Jira cloud seems to be something else than what a lot of people want
• Am I also waiting for this? Sure am.
• Do most of us watching this ticket want to hear how someone else would be so much better doing the vhosting? Probably not. 

We built internally a frontend for this 4-5 years ago to circumvent the problem back then. Would I have liked to have something from Atlassian at that time? Sure would, time to market would have been faster. Rather than venting on a ticket, I made the problem disappear. I am now also guilty of flexing you all on how much better I am doing vhosting......

In general, when you are a product manager for something you're pretty much always going to be hated on either by one group, some groups or everybody:

• you promise something and don't deliver on time for whatever reasons (like this ticket)
• you didn't promise anything and customers don't have any view into what's going to come down the road
• you promised something, delivered something, no-one is happy with the first version (I'm looking at you Atlassian access)
• customers disagree on company/roadmap priorities

I happened to watch the video where one of the product managers explains custom domains as well as data storage (so "EU data") roadmap. You'll be able to find the video, too. The slide deck that accompanied it was pretty convincing, at least to me. Also, that they have let 3rd party developers know is another sign that eventually the feature(s) will materialize.

If we completely ignore the technology aspect of this ticket, Atlassian seems to be doing quite alright - IPO was at $27.50 and 4 1/2 years later they're up at $141 or so. If you think this is a feature that will make or break the company you should short the stock (not legal advice).

Should be clear to everyone: that they have no interest in doing this, be cause the marketing value of having all their cloud customers advertise their platform every time they send a link to the end user.

Also ever noticed how much branding text and stuff they squeeze in everywhere in the platform for the end user to see?

So yeah, you basically pay full price for a product that you are forced to promote for free, hell you pay for it

I would totally agree with you, that 9 years is a long time to wait for any feature request, no doubt about that.  They have been more active on this one in the last 6 months though, so that's promising.

I was extremely excited about Refined, but ended up not using it. Can't recall exactly why, but probably because it had limited functionality.

@Stuart: you are correct in stating that it is very hard to introduce this at this late stage in the applications. Of course, this feature request is almost 9 (nine) years old. So one could argue they brought that upon themselves.

Hi Peter Dolkens,

Refined is an add-on for creating entire websites that sit in front of and can display some of your Jira content.  It is for customer facing websites that can expand on the use of the customer service portal, and is essentially a way of creating websites (which will always be able to have custom domains) that wraps around some Jira functionality.  This is not proof that Atlassian can do it themselves, by no stretch of interpretation.

So Atlassian isn't failing at security because of a hole, and they aren't using it as an excuse.  It's actually a difficult thing for them to implement on their stack.  Albeit sparse communications, they have given some explanation on the difficulties.

Source: I was invited late last year to a feedback session to look at one of their prototypes for custom domains.  As someone who has seen approximately how they intend to implement it from a UX view, I am confident they are working on this.

Final note: I initially had the exact same reaction to this; anger and frustration because I was short-tempered and naive. The reason was because something that we have taken for granted in so many other sites and systems was not possible here.  However, if you had any experience in a software development house offering customer-shared SaaS, you would understand the nuances of how applications are developed, and unfortunately how some applications are hard to introduce fundamental change to.  This appears to just be one of those cases. It might sound simple, and might look simple, but the solution is not simple. They are having to be extremely careful introducing something like this at this late stage in the applications life so as not to break other important features. Just think what you'd be posting if they introduced the feature but also introduced a major bug for customers raising urgent issues with your support team? How would that make you look to your customers?

Conclusion:

Chill out, be patient, and next time they reach out for involvement from the community to help move this along, do as I did and put your hand up instead of whinge.

@Peter Dolkens, mate, you have no idea how happy you made me with that link! If that works as I understand it, I can tell the man with the wallet that there is a solution, rather than there is a case with Atlassian. Thanks!

rkelledy - I understand the complications you face, but the simple fact is you've got marketplace vendors who are already offering custom domains as a (paid) feature on cloud instances.

https://marketplace.atlassian.com/apps/1218481/refined-for-jira-cloud?hosting=cloud&tab=overview

Either you're failing at security because the hole's already there, or you're using it as an excuse at this stage.

Hello,

Please be agile... The goal is not to provide all features at once. And that's the principals of Agile. I am migrating to the premium feature for that. Otherwise there is no point for me.

It appears that using the server version in a azure deployment is good alternative. This way azure manages cloud hosting and you have all the dns configurations that you would expect in 2010 (yes, we're in 2020). And also, (i dont know this for sure) it appears the pricing may be cheaper if you have more than a handful of users needing access to Jira software and Jira service desk. 

log into the azure portal, type Jira in the search bar and there is a wizard to get it setup. 

Maybe reach Cloudflare, you could rely on their secure configurations for this, manage the configuration from a Jira UI .

This way you can standarize the domain configurations instead of open this feature to anything else.

But the next gen product, the new Jira navigation, ALL of the features no one really cares about were so much more important than this one. 🤣🤣🤣 To be honest though... I sort of don’t ever want this issue to be complete because I love everyone’s commentary. 

Wow, this is so awesome. After almost a decade and this issue is still nowhere near finished! 

This is definitely an achievement in and of itself for Atlassian! 

Microsoft, Slack, NetSuite, and Google have all been able to do this very simple customer convenience and it seems that this has opened up so many rotting cans of worms with security underpinnings and badly designed auth code, or Atlassian dev teams are so siloed that you can't coordinate your left hand with what your right hand is doing.

Your lucky these customers don't move to your competitors by now.

~~~

By the way, my son was born in 2011, so I do get reminded each year this issue isn't resolved. Ha ha.

yes, cname will not work as of now base on my test too.

it seems that it is not possible to attach screenshot. I see message

Page unavailable

Your Atlassian Cloud site is currently unavailable.

Please check Atlassian Status for known problems.
If there are no known problems and your page hasn't appeared again in 5-10 minutes then please contact our support team.

So, today CNAME record issues.domain.com associated with domain.atlassian.net will produce 
 

is there any way to get better results?

Hi Jonas,
We did consider requiring customers delegate a DNS subdomain to us via NS records, but discarded that approach for a few reasons:

1) It doesn't improve the security posture - we wouldn't "own" the subdomain, we'd only control it while the delegating NS records are present and correct and that could change at any time.
2) We do not need the customer to create a lot of DNS records in our planned solution - currently only 2 per product. If we needed the customer to create a whole bunch of records (eg: CNAME, MX, SPF, DKIM, SSL Verification) then it might make sense to only ask the customer to create 2 NS records and we could then create the rest for them, but that is not the case.
3) Some customers are uncomfortable with the idea of delegating control of a subdomain. In our solution we ask the customer to create specific records. If we asked them to delegate a subdomain we could then create any records within that subdomain.

To be clear, the DNS part of this solution is largely a solved problem. At this stage we will be asking customers to create 2 CNAMEs per product they want a Custom Domain for - one for HTTP traffic and the other for Amazon Certificate Manager (ACM) to validate domain ownership before issuing the SSL certificate. We can leverage the HTTP CNAME to in turn provide MX, SPF and Simple Email Service (SES) validation records. We still have some investigation to do around DKIM records for outbound email.

I can‘t believe this is a big issue. Google did this for Firebase hosting. They validate your domain and create a Let‘s Encrypt certificate for your (sub)domain. I worked very well. More information (from the client side): https://firebase.google.com/docs/hosting/custom-domain

@gregoryc, Jonas is talking about subdomain delegation, it's a DNS thing and nothing to do with redirects.

Essentially Atlassian would "control" a subdomain you specify, e.g. atlassian.foo.com, where your domain is foo.com. They can then issue DNS-validated SSL certs for that subdomain, and control the A records to point to the server where your Cloud sites are tenanted.

Seems a fairly obvious solution to me too, but what would I know

Gregory, you can do https redirections with CNAME if the "host" server has a SSL certificate

Hi 3ea903ca3b70, what do you mean "an NS" record?

atlassian.net does not accept  https redirects via CNAME. 

Your  domain should  be known at least to their  SSL keystore.

We use other systems, where I had to add an NS record for a child domain to our DNS, so that the other system fully "owns" that child domain.
Just a tought if this could help here. In case of the other system it was also a matter of security as I run a small MSP business.

Kind regards,

Jonas

Update is much appreciated.  Thanks for sharing the complexity.  My sympathy dial has now been rotated clockwise.

Thanks Rob for sharing a detailed update.

Please keep sharing future updates in the future

thanks a lot for your update. I think most people just wanna know, what the next difficulties are that you're going to tackle.

So that helped a lot.

Thank you Rob - that helped a lot. Continue with regular updates here and everybody may get happy again.

Thanks Rob.  Your update and the detail within is much appreciated. 

agree with the previous people, how can this take ages?

@andrew w: I totally agree!  This is ridicolous and i have also been wondering for the last year why and how this garbage company still can be in business! I cannot think of another company or product as useless as Atlassian and JIRA. 

Very simple tasks is SO over complicated when it comes to JIRA! I always avvoid changing my forms - cus it's a big hassle everytime.

The pricing and licensing model is a big joke as well! 

I've solved Custom domain namnes via DNS-record + URL rewrite.  It's not 100% but its much better than waiting in vain, for Atlassian to the their shit together.... 

Sorry guys but I don't understand why this task is so difficult to do...

I mean... it's just a bunch of DNS CNAME records to validate the ownership of the domain for creating a SSL certificante and thats it!

I have made a similar task in my company for custom domains, and the level of difficult is easy.

I don't want to disrespect anyone who works on this product but... come on we are a LOT of people waiting for this feature and we will migrate to another solution sooner or later because this

@Justin Russell I think at this point calling it a complete and utter disaster would be putting it too mildly. It was really unprofessional nine years ago, after folks had been waiting for a year. Words fail me when it comes to this company, I have absolutely no idea how and why they're still around.

It's probably worth throwing this in the thread, though I'd be interested to hear if the timeline has changed at all. (I haven't seen any updates from Atlassian anywhere.) This is from slide 36 of the presentation linked in the October 2019 update.

Custom domains timeline

• Now: Developer preview
• Jan 2020: Jira Software early access
• Jul 2020: Jira Service Desk early access
• Sep 2020: Confluence early access

I will say that it's incredibly frustrating (and looks really unprofessional) to have to send our customers links to knowledge base articles at *.atlassian.net, but I have a feeling at least 3,942 other people agree with me there. 😏

Any updates?

Any Update on this topic? 

please update

Any news?

Any updates ?

Im sure that on Atlassian Summit 2019 (8 month ago) this was promised to be available

Actully by Nuwan, claimed to have solved (i think) the most voted ticket....or something 

Hope that this issue will not end in same way as Apple AirPower. Presented with aplaus at keynote but never introduced to market at all.  

Any updates on this?

Hi Simi,

Calendly link is broken FYI.

Update on 19/Nov/2019: Thanks to everyone that signed up so far!

We’re out of time to schedule more video calls, but I can also send across the draft designs for lightweight feedback over email. Again, just send me a message at sshaheed@atlassian.com if you’d like to participate.

Best,
Simi

Hi everyone,

We have some updates to our approach to custom domains we’re looking for feedback on. 

If you can spare 30 minutes to speak to us over video call in the next few weeks, please sign up here: calendly.com/vli-2/custom-domains-interviews. If you don’t see a time that works, email me to let me know you’re interested in taking part at sshaheed@atlassian.com

Thank you!

Simi
Designer, Atlassian

I would imagine - as has been mentioned before - if this was an issue which Atlassian had any intention of solving whatsoever it would have been done 7 years ago.

Many of us (after years of waiting) moved on after realising that Atlassian, a company famous for an issue tracker, had no serious intention of working on the most voted for issue in their own tracker; and is no longer the only provider of good tooling as may have been the case when JIRA/Confluence were relatively new.

Perhaps the best thing about this issue is that it forces customers to look seriously at other alternatives, which in many cases may not end up being a downgrade to anything Atlassian makes.

I would like to see custom domain support for standard licenses as well as premium licenses.

@Henry: I installed it this weekend, and it allows you to use your own domain name for the custom "portal".

@Tom, yes and it works fine.. I like it, but this wont solve this topic.. it is for customisation of the JSD en not to change domain names as far as I know.

Anyone tried this yet?

https://marketplace.atlassian.com/apps/1218481/refined-structure-and-theme-jsd-cloud?hosting=cloud&tab=overview

Only 1 3 star review.

Just had a 30 minute call with Simi and was happy to see some progress being made.

I would encourage all interested to let her know your requirements if you can attend a meeting.

Just received an email soliciting my feedback specifically for Jira Service Desk. Why on God's green earth does anyone in your marketing group think thats a good idea given the fact that the platform is missing core functionality such as this decade old ticket? Laughable at this point and will gladly write a public review.

Every time they ask for my feedback I give them the lowest possible rating and put a link to this issue in the text box.

Just received an email soliciting my feedback specifically for Jira Service Desk. Why on God's green earth does anyone in your marketing group think thats a good idea given the fact that the platform is missing core functionality such as this decade old ticket? Laughable at this point and will gladly write a public review.

Hi everyone,

We have some design prototypes of administering custom domains that we’re currently looking for feedback on, to make sure we’re on the right track.

If you can spare 30 minutes to speak to us over video call on 10 October or 11 October to test out the design, please sign up here: https://calendly.com/sshaheed/research-chat?month=2019-10

Thank you!

Simi
Designer, Atlassian

Dont get your hopes up. its not even in consideration. its in a "future" consideration. 

I think waiting on another product might be a quicker bet. 

There are features that have been completed that I am still waiting to be released. 

This ticket was created in 2011 so my guess is about a 15 year turn around time based on other tickets I've seen. 

When it comes to software they have to build features that will attracts new customers and only fix just enough to where we wont leave. If this was a priority they would have done something about it. 

Hey. We're waiting for this feature. Will be great to have this ASAP.

A CNAME with custom SSL certificate would be great for Jira Service Desk

I'd like to test/implement this - how do I get started?

Thanks for your input @calculon83.

My issue is that we run Jira Software, and Jira Confluence Server editions (and they're a little outdated).  I can't configure Jira Service Desk Cloud to use a Jira Confluence Server space as the knowledge base.  It only gives me the option to use an Jira Confluence Cloud space.

Multiple e-mails - I have tried this, with e-mail forwarding from our priority e-mail to our regular e-mail.  There is no identifier on the ticket created that shows it came through the priority e-mail first.  It appears that I can only use separate projects for separate e-mails.  One e-mail per Project is fundamentally (in my opinion) a functional oversight.

I appreciate your response though, I've been looking for solutions for this for weeks.  I think now, i'm going to have about 6 JSDC Projects, that all send their issues inter-project just to handle it.  I'm not looking forward to it.

Hey @stuartmills, we just set this up and were able to connect Jira issues from our project to the SD cloud issue and were able to setup a space in confluence for our knowledge base for SD cloud. Multiple emails, I would see up a forwarding rule from the inboxes, and as for the custom domain, that's just disappointing.

Name one other Service Desk competitor's solution that doesn't have this feature already out of the box.

I wish we knew this before we commenced on the journey and I've been putting weeks of effort into customising and paying for addins and solutions.

Who would have thought that Jira Service Desk Cloud had such difficulties doing such incredibly basic things?

• Custom Domain (support.company.com) - basic, not possible.
• Let Issues in SD Cloud link to Issues in Software Server - basic, not possible.
• Use Confluence Server spaces as the Knowledge Base for SD Cloud - basic, not possible.
• Multiple e-mails into one SD project - basic, not possible.

I'm incredibly disappointed after 'talking up' the software inside the business here - my mistake.  I have to justify this choice I've made, and all of these constraints are making it very difficult.

My money's on hitting 10 years before any code actually takes shape. Atlassian needs to be consistent in their pace to keep brand image intact, 10 yrs anniv for this issue would be just that. 😉

"we’re now in active development"—Wow, after only 9 years! You're bound to hit the sonic wall, brace for impact.

I guess we should all rejoice this issue is considered medium, not low priority.

Once again, Atlassian are gouging their customers by forcing them to pony up more money for features that are available in the basic tier of your competitors.

First it was SSO being bundled in with Atlassian Access, now custom domains go to the "premium" level. Rapidly becoming a product I can't recommend anymore.

Victoria Li, if this is being worked on per your desc update, why does it have no assignee still?

@flaccid— 👏👏👏👏👏

https://www.businessinsider.com.au/atlassian-says-the-cloud-is-its-future-as-it-makes-sweeping-changes-to-its-flagship-products-and-pricing-2019-9 hi Scott, I do find it hilarious that you say cloud is your company's future but you can't even do this basic cloud feature after 8 years of customer complaints. Happy to catch a water taxi to your house to discuss.

Using CNAME redirection causes SSL certificate validation failures.  The certificate is a wildcard of atlassian.net, which doesn't match with your own domain name in the CNAME entry, so CNAME isn't really a valid way to accommodate this.

Ricardo, you need to use both.
Create an A record on your DNS, pointing to your IIS or a 3rd party ulr-redirect service.
Create a redirect and you're off.

Not the best solution, but far better than what Atlassian is offering.

@James Frank,  did you used your own DNS or did you sed a 3rd party (ex.: https://www.easyredir.com/free-url-redirect/ ) ?

Ricardo Sousa da Silva–you can already do that by simply hosting a redirect on your own domain. Atlassian isn't doing it for you, but you can do it for yourself. We've got that set up. Reach out if you have questions.

Is there any recent update for this issue?

Is it possible to accept a redirection in this case? For example add the ability to customers create/maintain their own A or CNAME entry (https://jira.acme.com) and redirect for its cloud instance (https://acme.atlassian.net)

@gq723xh Oh trust me, the entire world is marveling at Atlassian's inability to deliver such an essential, yet very basic feature.

Every single one of my ticket systems, remote management, help desk or other portal-based software offers custom domains and has been for years (not having that doesn't make sense after all). Granted, they might have you choose a higher tier or pay extra, but you get it one way or another. With Atlassian, it's out of reach no matter how much you pray or pay. How they ever managed to become a world player is completely and utterly beyond me.

Honestly I'm baffled this functionality is not available. Given the heavy push towards the Cloud version, it's quite sad how badly Cloud is lacking.

Oh dear. I tested this software now for days. Seeing if everything i require is supported. I NEVER expected, that I have to send links to MY customers with xxx.atlasian.net in the URLs. That is a MAJOR issue. Some of our customers might even think this is spam (in germany they are kind of paranoid).

Since this is open for years and has the highest vote by far (10 times more votes then place 4). I believe this is something you are NOT willing to change at all. It sounds more like "we telling our customers we change it to keep them silent". Oh dear. I am looking into competition right now.

Because of this and the not being able to change the sending email address for emails from Jira Service Desk in the Cloud - we've decided to move away from JSD and across to something else

Hopefully for everyone else's sake here they sort this one out soon.

Thank you for your explanation  antonio.perez101045794.
Let's vote and wait  

Thanks,

Hi @Tran Van Huu,

No, I meant they allow us to change from AAA.atlassian.net to BBB.atlassian.net.

Hi antonio.perez101045794, 

Based on your recently comment, does it mean that now Atlassian allows user to custom their domain for cloud.

Like we have AAA.atlassian.net and now they can help us change to AAA.net or AAA.com, am I right?

Thanks,

Hello,

We contacted  https://support.atlassian.com/contact to rename our domain name and everything went fine. The process took less than 10 minutes.

Also, our old URL redirects to the new one, so we don't have to notify our users.