-
Suggestion
-
Resolution: Fixed
-
2,116
-
Problem
Today, you can sign up for certain Atlassian cloud products (Jira Software, Jira Service Management, and Confluence) under the subdomain of your choice. For example, if your company is Acme, you can host these products under acme.atlassian.net
The scope of "custom domains" on this ticket is to allow customers to use Atlassian cloud products on their own second-level domain, i.e. jira.acme.com or acme.com/confluence
Hi everyone,
As we shared in our last update, we will be closing this ticket now that custom domains for Confluence, Jira, and Jira Service Management are generally available. If you have any questions, please reference the support documents or raise a support ticket.
Going forward, this ticket will be moved to the ‘Done Issues’ section and comments will not be monitored.
Thank you,
John Hooper
Product Manager, Confluence
Hi everyone,
Custom domains are now generally available for Confluence on Premium and Enterprise cloud plans!
If you’re ready to get started with custom domains, follow these instructions. As noted in our last status update, we will be closing this ticket 30 days from today. After that time, we ask that you raise a support ticket with any questions.
Thank you,
John Hooper
Product Manager, Confluence
Hi everyone,
My name is Moinak Chatterjee and I’m a Senior Group Product Manager at Atlassian. We have a few important updates on custom domains.
Custom domains for Jira and Confluence
Custom domains are now generally available for Jira and will become generally available for Confluence starting in Q3. Custom domains for both Jira and Confluence will be available on Premium and Enterprise cloud plans. The rollout for Jira started today and will continue gradually over the next two weeks.
Custom domains are an administrative capability that allow organizations to use their own domain name to host Atlassian products. For example, using go.jira.acme.com instead of acme.atlassian.net. Using a customer-branded URL instead of an Atlassian-branded URL helps make sites more discoverable, accessible, and uniquely yours, since they’re based on the organization’s domain rather than Atlassian’s. Custom domains join the family of advanced administrative capabilities that are the foundations of our Premium offering and are also included in Enterprise plans, alongside features like sandbox and release tracks.
Custom domains for Jira Service Management help centers
For Jira Service Management (JSM) help centers, discoverability and branding are of the utmost importance so that your customers can get the help they need as quickly as possible. Custom domains for JSM help centers enable better customer service rather than better administration, which is why they will continue to be available on all paid cloud plans.
Getting started with custom domains
If you’re ready to get started with custom domains for Jira, follow these instructions. We will provide an update on this post when custom domains for Confluence become generally available.
If you are not already using a Premium license(s), you will need to upgrade to Cloud Premium to enable custom domains for Jira or Confluence. If you’re also looking for advanced scale, security & compliance, analytics, and support, we recommend you evaluate the Cloud Enterprise plan.
URL redirects for even more flexibility
We’ve heard your feedback and understand that many of you are looking for more flexibility in how you configure custom domains, which is why we also support URL redirects.
In designing the custom domains solution, we’ve been intentional about balancing security, customization, and open collaboration. Having a two-level domain plays a critical role in making our solution resilient to potential man-in-the-middle (MITM) attacks. At this point, we do not have plans to revisit the two-level subdomain construct, but customers who would like to use a shorter URL can set up a URL redirect. If you choose to use a redirect, you can create links with a shorter, fully customized base URL that redirects your users to the full URL.
What’s next?
Custom domains for Jira and Jira Service Management are generally available today. Custom domains for Confluence will become generally available in Q3. Therefore, we will close this ticket 30 days after Confluence custom domains become generally available. This will give you time to use this ticket to ask questions about how to use and access custom domains. After that time, we ask that you raise a support ticket with any questions.
We know many of you have given feedback about custom domains in the past. If you have additional feedback, we welcome you to share your candid feedback and concerns. We’ll be listening! But as a way to keep the dialogue productive, please note that we will prioritize addressing comments related to the functionality of custom domains and how to use them.
Best,
Moinak Chatterjee
Senior Group Product Manager, Atlassian
Hi everyone,
Now that custom domains for JSM Help Center is generally available and custom domains for Jira is in early access, I’m excited to announce another milestone for the custom domains program.
Early access - custom domains for Confluence
We’re launching the Early Access Program (EAP) for custom domains for Confluence Cloud. Bringing custom domains to Confluence will make it easier for your team members to find and access your site.
To join the EAP, simply follow these steps:
- Visit our EAP signup page
- Fill out the form with your details
- Be on the lookout for a confirmation email with further instructions
Please note that we will limit the number of participants for this EAP so that we can properly manage feedback that comes in as part of it.
Support for URL redirects
I also wanted to re-share information on the option to add URL redirects, which can offer more flexibility and allow you to share a shorter URL with your team or customers. If you choose to use a redirect, you can create links with a shorter, fully customizable base URL that redirects your users to the full URL. For more information, please visit Community or the Atlassian Support Documentation.
Thank you,
John
Custom Domains for Jira - Early Access Program
We are thrilled to announce the launch of our highly anticipated feature - Custom Domains for Jira! We are inviting you to join our Early Access Program (EAP) and be among the first to explore and provide feedback on this new feature.
Custom Domains is designed to give you more control over your Jira instance and enhance your branding. This new feature allows you to customize your Jira domain to match your company’s domain, making it easier for your team members to remember and recognize.
To join the EAP, follow these steps:
- Express your interest on our EAP signup page - Registration link
- Fill out the form with your details.
- Await your confirmation email with further instructions.
Please note that the Early Access Program for the Custom Domains feature is limited to a select group of users for now. We encourage you to sign up as soon as possible to secure your spot. We will further communicate regarding the status of your request post mid-January after analysing your response.
Once you're part of the EAP, we ask that you use the Custom Domains feature and provide us with feedback. We appreciate any insights you can provide about your experience, whether they're about usability, performance, or any other aspect of the feature.
We are committed to making the Custom Domains feature the best it can be, and we are eager to receive your valuable input. We believe that with your help, we can create a more personalized and effective Jira experience for all our users.
If you have any questions about the EAP or the new Custom Domains feature, please don't hesitate to get in touch with us at Custom Domains Support
Best Regards,
Prashanth M
Product Manager, Jira Platform
Hi everyone,
Custom domains for Jira Service Management Help Center paid customers have exited beta and generally available! We also have progress to report on work to introduce more flexibility in your custom domains and on a new early access program for custom domains for Jira products.
Value of custom domains for your JSM Help Center
Implementing your own branded URL for your Help Center will make it easier for your customers to find and recognize your brand. Operationally, your customers will have an even more seamless experience getting the help they need from the right places. Greater discoverability enables more self-provisioned help and less time required for your team to manage requests.
Introducing more flexibility in first level subdomains
Since announcing the open beta for this feature in August, we’ve been working to introduce more flexibility in how you implement your branded URL. Currently, you’re prompted to select from a list of keywords for your first level subdomain, but that part of the domain will soon also be free text. Once first level subdomain flexibility is shipped, it will be available across all future custom domain launches for your various Atlassian products.
Early access - custom domains for Jira
Last week, we announced the launch of the Early Access Program (EAP) for custom domains for Jira - including Jira Software, Jira Work Management, Jira Product Discovery and the agent experience in Jira Service Management. If you’re interested in joining the program, please refer to this comment and complete this registration form.
What’s next
As we mentioned in August, we’re releasing custom domains support on a per-product basis. Please visit the Atlassian Cloud Roadmap to follow along on progress. We will introduce the per-product leaders in a future update.
Best, Luke
Hi everyone,
As of August 1, 2023, we have released custom domains into open beta for all paid Jira Service Management Help Center customers. With this release comes greater discoverability, customization, and ease of use for your organizations' admins, teams, and customers. For details on the release, please see the Jira Service Management community article.
Where we are now
With our open beta underway, we’re happy to share that we are seeing broad-based adoption across our customer base and a high completion rate across customers who begin to setup up custom domains for their organization. Please continue to use the "Give feedback" option inside Admin Hub, or email custom-domains-working-group@atlassian.com
[|mailto:custom-domains-feedback@atlassian.com], or leave a comment here. We continue to monitor the open beta results and your feedback to inform our approach for what's next.
What’s next
Our approach is to release custom domains support on a per-product basis for Jira Software, the Agent Experience in Jira Service Management, and Confluence.
As a reminder, the timeline for when we release support for each product will vary. You can visit our cloud roadmap or continue to watch this ticket for additional progress updates.
Thank you for your continued engagement. We will post another update in the coming months.
Best, Luke
Thank you for your engagement on our last update. We know how important it is for you to have a clear and detailed understanding of the technical reasons behind the constraints and how they enhance your security experience with custom domains. Please see our latest update with more details on the security consideration and our support for URL redirect.
All the best, Luke
Hi everyone,
This past quarter, we engaged a number of existing customers, and specifically Atlassian cloud admins, for focus group sessions. We did so to validate our direction and early admin experience designs for feedback.
We shared these preliminary designs in the Atlassian Enterprise Community. Please refer to our update here.
We will be back next quarter with the latest.
All the best, Luke
Hi everyone,
I am bringing you the latest update on the Custom Domains work. The leaves may be changing around the Atlassian San Francisco office, but I’m happy to report our custom domains work is still green (and on track!) for early access in 2023.
Shipping custom domains requires extensive to changes to both our products and numerous pieces of our underlying shared cloud infrastructure. Among product teams, the Jira Service Management team is currently farthest along on this journey. As such, I’m excited to announce they have recently completed detailed, technical scoping and are beginning the implementation to bring Custom Domains to JSM.
In our last update, we mentioned that the approach to Custom Domains requires the enablement of new security measures. As many of you know, we operate under a multi-tenant SaaS architecture, which allows for better scalability and efficiency, minimizes security risks, among other benefits. This architectural approach also allows a single Atlassian account to be granted access to data across any number of Atlassian organizations, products, and marketplace apps. With the introduction of Custom Domains, we plan to add guardrails for the new third-party traffic controls (e.g. DNS resolver, Certificate Authority, etc.) between the user and the Atlassian systems.
As a result, we are focusing on added security measures around auth tokens, improved security threat detection, and increased user awareness when they encounter a custom domain. We are also building out corresponding admin controls for managing custom domains in Admin hub.
While we are committed to bringing Custom Domains to you as quickly as possible, we must do so with security and the safety of your data in mind. On behalf of the various teams contributing to this feature, thank you for your patience and continued support. Stay tuned for the next update next quarter.
Best regards,
Luke Liu
Senior Product Manager, Admin Experience
Hi everyone,
I am checking back in with the latest update on this feature. Apologies for the slight delay; I wanted to ensure our next communication accurately reflects our scope and progress.
Since April, we have continued working on foundational platform building blocks, engaged our various Jira and Confluence product teams to align timelines, and partnered with our security team to advise on our work-in-progress builds. I am happy to report we remain on track for early access in 2023.
Custom domains has been a multi-year undertaking, and we are confident in that our current approach will deliver the benefits that you have been waiting for. This approach is built upon Atlassian’s modern cloud platform, with new security measures enabled. While using custom domains with Jira and Confluence on-premise is relatively straightforward, implementing custom domains in a multi-tenant SaaS architecture with hundreds of thousands of customers requires a high degree of care. We are working closely with each product team to ensure that all existing cloud products will continue to work as expected in a tenant with custom domains enabled.
Personally, I am really excited about this progress, and appreciate your candid comments and feedback. Thank you for your partnership, next update coming this fall!
Best regards,
Luke Liu
Senior Product Manager, Admin Experience
Hi everyone,
I’m Luke. I recently started at Atlassian, working with c6c23291180e to drive the custom domains efforts, and continue our quarterly updates.
In our last update, we shared our focus areas at the conclusion of 2021. These included: internal implementation approvals, a final staffing plan, and the beginning of risk mitigation for execution. This quarter, we continued this progress, and we are still on track to deliver custom domains in 2023.
Most recently, we have built a team that will focus exclusively on delivering custom domains. Engineering work has kicked off on platform building blocks that will support custom domains across the Atlassian product portfolio. Delivering custom domains will require the collaboration of multiple teams across Atlassian, platforms or products, and we continue to build momentum across the board. Additionally, safeguarding our customers' data is our topmost priority, so we are also taking extra precautions to ensure that exposing custom domains controls does not introduce new security risks.
Thank you for you continued interest and feedback. Your enthusiasm drives the program’s importance and urgency. Look out for our next update in July, and please feel free to share any feedback with me directly: lliu2@atlassian.com
Best regards,
Luke Liu
Senior Product Manager, Admin Experience
Hi everyone,
As promised, we are providing another update on custom domains as we enter into 2022 and look ahead.
I am pleased to communicate that we are still on the trajectory to deliver custom domains support in 2023. In the last two months, we have secured the final round of internal approvals on the implementation approach, finalized our staffing plan, and started to de-risk our execution plan by securing commitments from teams that we expect to contribute to the build.
As before, we will continue to be transparent and provide timely updates. As the project is starting to pick up speed, we also intend to increase the frequency of these updates, delivering them on a quarterly basis.
On behalf of the Atlassian team, we take your feedback seriously and understand both the frustration and the urgency. We are working hard to create the best overall experience for as many customers as possible, in line with our company values. You can share your feedback with me directly: ibagrak@atlassian.com
Best regards,
Ilya Bagrak
Group Product Manager, Admin Experience
Hi everyone,
I wanted to share an update on our progress, as we are acutely aware of the need for custom domains for many of our customers.
Atlassian reevaluates our product priorities on a quarterly basis, and we have just wrapped up another cycle of planning. I am proud to say that since the last update, my team has helped ship self-serve site rename (another long asked for feature set) and are about to ship the much-needed improvements to custom domains for email. We’ve also been working hard to ensure that admin.atlassian.com continues to meet the performance needs of our largest and most complex cloud customers.
These efforts illustrate the investments we’ve made in admin controls and performance, but it’s clear we need to do more. Unfortunately, this will delay our ability to invest in custom domains to the extent we originally planned. We are currently on a trajectory to deliver custom domains support in 2023 and are exploring options to accelerate the effort as well as to deliver incremental solutions ahead of that time.
We will continue to be transparent and provide timely updates, even when the news is not what we would prefer to share.
On behalf of the Atlassian team, we take your feedback seriously and understand both the frustration and the urgency. We are working hard to create the best overall experience for as many customers as possible, in line with our company values. You can share your feedback with me directly: ibagrak@atlassian.com
We plan to provide the next update on this feature by January 2022.
Best regards,
Ilya Bagrak
Principal Product Manager, Admin Experience
Hi everyone,
I work with dmeyer and lead Atlassian’s custom domains team and will take over updates on our progress going forward. I know many of you have been eagerly awaiting one!
In the last 6 months, the team has reviewed our previous technical efforts on custom domains implementation, alongside general security improvements implemented by major web browsers, and we’ve achieved internal consensus on the new approach to deliver this feature for our Jira and Confluence cloud products.
I apologize that this update has not come sooner, but we have been quite busy taking our recommendation through internal security and architectural reviews, and I am happy to report that we are well on our way to fleshing out the execution plan. We will ramp up on execution over the new several months and continue to plan for an EAP for custom domains next year.
Security for our customers remains our highest priority and a place where we are unwilling to compromise. While we understand and have deep sympathy for the urgency of delivering custom domains, our focus in the last six months has been finding a more feasible implementation that meets customer requirements, without putting our customers at risk.
I also appreciate that many of you are puzzled by why something that appears so trivial at first glance would be so hard to deliver in practice. We are committed to helping our customers understand the unique complexity of getting a solution out there quickly and safely and are working on a blog post that will unpack some of the underlying technical challenges and constraints we’ve had to overcome.
Across Atlassian, we are committed to investing where we can have the greatest impact for the most customers possible. I encourage you to check out the full scope of our plans on our public roadmap, custom domains included.
On behalf of the Atlassian team, we take your feedback seriously and understand both the frustration and the urgency. We are working hard to create the best overall experience for as many customers as possible, in line with our company values. You can share your feedback with me directly: ibagrak@atlassian.com
We plan to provide the next update on this feature by January 2022.
Best regards,
Ilya Bagrak
Principal Product Manager
- blocks
-
- Closed
- is related to
-
MP-236 Installing a connect app using app descriptor in Confluence cloud that has custom domain fails
-
- Closed
-
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
-
PCS-266765 Loading...
-
- links to
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- relates to
-
-
- resolves
-
[CLOUD-6999] Allow custom domains for Cloud apps
Hi everyone,
My name is Moinak Chatterjee and I’m a Senior Group Product Manager at Atlassian. We have a few important updates on custom domains.
Custom domains for Jira and Confluence
Custom domains are now generally available for Jira and will become generally available for Confluence starting in Q3. Custom domains for both Jira and Confluence will be available on Premium and Enterprise cloud plans. The rollout for Jira started today and will continue gradually over the next two weeks.
Custom domains are an administrative capability that allow organizations to use their own domain name to host Atlassian products. For example, using go.jira.acme.com instead of acme.atlassian.net. Using a customer-branded URL instead of an Atlassian-branded URL helps make sites more discoverable, accessible, and uniquely yours, since they’re based on the organization’s domain rather than Atlassian’s. Custom domains join the family of advanced administrative capabilities that are the foundations of our Premium offering and are also included in Enterprise plans, alongside features like sandbox and release tracks.
Custom domains for Jira Service Management help centers
For Jira Service Management (JSM) help centers, discoverability and branding are of the utmost importance so that your customers can get the help they need as quickly as possible. Custom domains for JSM help centers enable better customer service rather than better administration, which is why they will continue to be available on all paid cloud plans.
Getting started with custom domains
If you’re ready to get started with custom domains for Jira, follow these instructions. We will provide an update on this post when custom domains for Confluence become generally available.
If you are not already using a Premium license(s), you will need to upgrade to Cloud Premium to enable custom domains for Jira or Confluence. If you’re also looking for advanced scale, security & compliance, analytics, and support, we recommend you evaluate the Cloud Enterprise plan.
URL redirects for even more flexibility
We’ve heard your feedback and understand that many of you are looking for more flexibility in how you configure custom domains, which is why we also support URL redirects.
In designing the custom domains solution, we’ve been intentional about balancing security, customization, and open collaboration. Having a two-level domain plays a critical role in making our solution resilient to potential man-in-the-middle (MITM) attacks. At this point, we do not have plans to revisit the two-level subdomain construct, but customers who would like to use a shorter URL can set up a URL redirect. If you choose to use a redirect, you can create links with a shorter, fully customized base URL that redirects your users to the full URL.
What’s next?
Custom domains for Jira and Jira Service Management are generally available today. Custom domains for Confluence will become generally available in Q3. Therefore, we will close this ticket 30 days after Confluence custom domains become generally available. This will give you time to use this ticket to ask questions about how to use and access custom domains. After that time, we ask that you raise a support ticket with any questions.
We know many of you have given feedback about custom domains in the past. If you have additional feedback, we welcome you to share your candid feedback and concerns. We’ll be listening! But as a way to keep the dialogue productive, please note that we will prioritize addressing comments related to the functionality of custom domains and how to use them.
Best,
Moinak Chatterjee
Senior Group Product Manager, Atlassian
Hi everyone,
Custom domains are now generally available for Confluence on Premium and Enterprise cloud plans!
If you’re ready to get started with custom domains, follow these instructions. As noted in our last status update, we will be closing this ticket 30 days from today. After that time, we ask that you raise a support ticket with any questions.
Thank you,
John Hooper
Product Manager, Confluence
All comments
It's not even April Fools Day, but this must be a bad prank. Did they even read the "scope" as listed on the ticket?
"The scope of "custom domains" on this ticket is to allow customers to use Atlassian cloud products on their own second-level domain, i.e. jira.acme.com"
This whole ticket is a disaster. Atlassian should have created a new ticket with the intermediate scope and kept his one as stated, not the reverse. It goes against best practice to just change a scope to fit your desired means of implementation.
There is not a single user who wanted your intermediate step or who agrees that this ticket should be marked as done.
"comments will not be monitored" hahaha
Do you really read the comments?
The resolution has mistakenly been set to 'Fixed'Hi everyone,
As we shared in our last update, we will be closing this ticket now that custom domains for Confluence, Jira, and Jira Service Management are generally available. If you have any questions, please reference the support documents or raise a support ticket. Going forward, this ticket will be moved to the ‘Done Issues’ section and comments will not be monitored.
Soon this ticket will be closed, so I guess we shoud move party to the ticket here https://jira.atlassian.com/browse/CLOUD-11811 requesting one subdomain custom domain and vote there
62c32a53ff47 Thank you for your interest. But I'm already deeply disappointed, as is everyone else.
First of all, the issue with third-party apps should have been predictable to the development team, given the last 13 years of development. For example, I've already used third-party services like 'cloak.ist' to serve Confluence with a custom domain, and I've also used 'cloudflared' to serve Confluence with a custom domain, and these same third-party apps caused issues, so it's hard to believe that the development team couldn't have predicted these issues before launching the service.
I have already removed the Confluence custom domain feature because of an issue with the JSW API throwing DNS errors and becoming unavailable, and the JSW API is working fine again at this point. I have no intention of re-enabling the custom domain feature in Confluence to reproduce the issue, as it causes a number of issues in my workflow when the JSW API is misbehaving. Wouldn't it be possible for you to reproduce the issue yourself?
You don't even mention the issue of broken links through custom domain when I stop using them, and this behavior in particular makes it very difficult for me to decide to try using custom domains again. As long as I don't lose ownership of my domain and keep my existing CNAME settings, I should be able to stop using custom domain and still be redirected without the links breaking. I have no intention of using the custom domain feature again before then.
Finally, the second-level subdomain I've seen in action makes me feel ashamed and helpless every time I use Confluence. I am deeply grateful to the team that has been working on this feature for the past 13 years. But for the sake of my own mental health, I will no longer be using this feature. I've convinced myself that I don't need custom domain anymore, and now I'm done with them.
Thank you 3649a879e76a . Regarding the items you mentioned:
re: third party applications - This is a known issue that our team is investigating. Here is a JAC ticket for the item if you would like to be informed of updates
re: JSW APIs not working and Confluence links breaking when custom domains are discontinued - are you able to submit a ticket to our support team (ideally with images / videos of what's happening) so that we can investigate these items further? These are behaviors that our team is not currently aware of and would like to better understand what you're running into
We implemented this recently for our JSM product, and it is not what I expected or hoped for.
The full URL for our instance now has become: https://servicedesk.atlassian.acme.com/servicedesk/customer/portals
That is mighty long and ugly.
We added a redirect, but that only works to get you to that ugly two-level custom domain...
For us, and for 99% of the customers, the challenge will be coming up with a sensible two-level custom domain name.
Custom domain currently have a number of issues. Please be aware of the following issues before applying them to live services:
- Several third-party applications that rely on web addresses will stop working.
- Jira APIs will stop working with DNS errors (I set up a custom domain in Confluence, but Jira is affected).
- If you discontinue your Confluence custom domain, links that were using the custom domain will break.
Another thought... Let's just assume, for the sake of discussion, that Atlassian has fundamental architectural debt in their platform that necessitates two tokens. Why can't you handle that transparently to the user? For example:
String host = "confluence.woojinkim.org"; String[] parts = host.split("\\."); int len = parts[0].length()/2; String tokenOne = parts[0].substring(0, len); String tokenTwo = parts[0].substring(len);
Nobody in their right mind wanted two-level custom domains. Lmao Get out of here. Please, find one comment in this thread or anywhere else on planet Earth where someone was clamoring for that. Nobody even thought about it before Atlassian invented such an absurd thing.
I would be equally as shocked if Atlassian announced that my house would need to be set fire to have a custom domain because that makes just as much sense as a two-level custom domain.
Also, why the charade of waiting 30 days to close the ticket? If you're going to ignore everyone's feedback you should close it immediately.
62c32a53ff47 - You could not possibly be more deaf to what your customers are telling you.
6823c0c617ed - The time for your perspective passed a decade ago. This thread is more absurd than most Dilbert comics. The majority of customers on this thread are saying that this isn't what they want, and Atlassian has been very clear that they intend to close the issue regardless. They are acting in bad faith.
I will never again willingly use an Atlassian product; They are dead to me.
Bryan Guffey, it's not just that they didn't implement it in the way that we want them to, they didn't implement in the way that they said they would implement it.
We are not stupid either. Many of us are application developers and have implemented this exact feature in our own products. We understand that the "technical reason" we were given it's woefully incomplete and makes no sense. The only context which would explain why their excuse make sense is that they have fundamental architectural technical debt in their platform. Yet they would never admit this, in spite of their alleged core value of "No Bullshit".
It didnt implement what description of this feature wants. This feature wants `jira.acme.com` not `jira.atlassian.acme.com` (which now presents a question are we in Atlassian or Acme). So closing this feature and claiming that it is implemented because it now provides what they want in reverse (acme.atlassian.com - is now Jira domain, but no idea how you make for another product in this case). So for them to bluntly state this feature is implemented and will be closed in 30 days, although it is not and you have around 8000 people on it (which are just probably single representatives of companies ITs), is pure mocking of the users.
And their description is a single statement: "because of security", without explanation just insults lets say 4000 people on this issue who know what security means and know that if you want to put security anywhere, you need to explain how, where, why.
I have to be honest, what most people here are complaining about is that Atlassian did implement the requested feature, they just didn't implement it in the way you wanted. That's a fair complaint. But if we do what is rational, which is consider that the folks at Atlassian are not stupid (assuming people are stupid always leads you to get the answer you want, so it's a bad tactic), there must be a good reason for this, and since Atlassian depends on the subscriptions of its customers for revenue, I sincerely doubt that they intentionally implemented a solution that pissed off a bunch of users.
Therefore, what everyone here is asking for is a better communication of why the feature was implemented in the way it was. However, why would Atlassian take the time to provide that information if the users on this issue will simply deny that as the reason, instead of saying, "Well, I don't like it, but I understand it."
I encourage folks to be focused in their feedback and their requests. The product managers and developers at Atlassian are people too, and treating people with kindness, respect, and a assumption of good intentions is how you get what you want. Trust me, I have been very pissed at Atlassian before, but I got what I wanted because I was factual, concise, clear, and called back to their values.
If there is a real reason this solution does not work (like, functionally, fails for your use case), I'd be fascinated to hear it. If it's just, "I don't like the way it's implemented," cool, but that's not the same as "not implemented."
(waiting for the first person who comments and calls me a shill for Atlassian, lol - I've been in the ecosystem longer than nearly anyone (17 years) and have had plenty of battles with the company and its leaders, but tilting at windmills has never actually served the goals of getting what you want)
d626d408e615 some of us actually are migrating from Atlassian. It just takes time but the wheels are turning. It wasn't just one issue for us. Over the past 5 years, Atlassian has created a record of decisions that have harmed us, and we finally reached a boiling point. They no longer "get it."
At least, we have here a perfect example of enshittification of SaaS-providers and how it evolves through the least 13 years.
Yeah, sure, close this ticket. Just make sure the resolution is set to 'Will not be fixed', as the customers request will not be implemented at all.
We'll make sure to open a new ticket requesting the very same feature we asked for in this one: The ability to set a custom domain for our instances. Forcing a three dot domain is by no means custom.
ca4cc226779f I fully agree.
But bottom line, Atlassian can afford this behavior, because we all stick around.
There is no need to listen to customer requests, if the customers stick around anyway.
Then, there is NO problem to be solved.
Have a complaining customerbase is way better than NO customer base.
The choice is ours
Closing this ticket, the only thing that is important. What about the issue? The complete disregard for the userbase, coupled with an insatiable greed for profit, is truly unfathomable.
https://confl.uence.woojinkim.org/
Wow. This is my cus.tom do.main for confl.uence. It lo.oks so co.ol and ni.ce.
very.thanks.
Hi everyone,
Custom domains are now generally available for Confluence on Premium and Enterprise cloud plans!
If you’re ready to get started with custom domains, follow these instructions. As noted in our last status update, we will be closing this ticket 30 days from today. After that time, we ask that you raise a support ticket with any questions.
Thank you,
John Hooper
Product Manager, Confluence
the ticket was created in Jul/08/2011, wow, 13 years to resolve a ticket what an excellent customer service experience, we are also moving to some other alternatives and encouraging our customer to not use consume this company products, unfortunately some of our partners still use Atlassian, so we need to use the new crap of cloud version, the old server version was 1000 times more intuitive a beautiful, this company is going backwards with the management every year
c8abf7e95ba8 Thank you. I already submitted it as https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-42716 and sorry for the noise.
Hi bd7e3e2a0b56 - Today, custom domains only support session tokens, and do not support API tokens. We are working to add this information to our Support Documentation.
87f578d1c214 - I am triaging this issue internally and will report back with more information ASAP.
Installing application from atlassian-connect.json descriptor, using upload feature, results in error:
Access to XMLHttpRequest at 'https://{redactedNativeSubdomain}.atlassian.net/wiki/rest/plugins/1.0/com.atlassian.plugins.confluence.markdown.confluence-markdown-macro-key' (redirected from 'https://{{{}
{redactedCustomDomainSubdomain}{}}}/wiki/rest/plugins/1.0/pending/cd34127b-0f9f-4990-b06f-5284ce92c727?_=1719011123048') from origin 'https://{{{}{redactedCustomDomainSubdomain}{}}}' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
According to our dev, this is bug in UPM (Universal Plugin Manager). Let me know if you think I should also report it using https://developer.atlassian.com/support
Hi,
We are facing an issue when try to authenticate to an UI resource using API Token when the site is with a custom domain. Works if a session cookie is provided, but fails to authenticate with email:apiToken provided in Authorization header. Any help?
903c507d134e - you will need a Premium or Enterprise plan to enable a custom domain for Jira and Confluence (Jira available today; Confluence coming soon). You will not be able to create a custom domain on a Jira or Confluence Standard plan. To set up a custom domain on a Premium plan, please follow these instructions.
Moinak,
This 13 year journey to end up with a solution that no one wants has left a terrible taste in my mouth. We have added finding a replacement to Atlassian products to our roadmap and I will not be looking to Atlassian for any future companies. This is really sad because the products in general are relatively good, but Atlassian does not listen on this issue and in plenty of other ways.
Best of luck,
Aaron Kraft
Chief Technology Officer
RxLive, Inc.
How it will work if one application is in premium and another application is standard license?
Here I was all excited to try custom domains. But no, I can't, because we don't pay for Jira Premium.
Not that I'd want to anyway, based on the documentation I'm going to have to have a long and complicated URL that makes no sense to my staff or customers.
Come on Atlassian, What ever happened to "Don't F#@K the customer" ?
That's literally all you've done on this project. The feature is not what we asked for, and you want us all to upgrade to premium.
I think you mean "Don't F#@K the customer"
Basically it's very simple.
We have complained for 13 years.
For Atlassian the concept is: "Better a complaining customer, than no customer"
Since we all stick around, there is no reason to act. Since they don't feel the impact (customers leaving).
So, why would this be a priority?
OK, so let me get this straight. We've been asking for custom domains for 13 years. After all those years, you come up with a solution that is not really what was requested. You made it available through EAP. Silly people like myself have helped you out getting the product ready for GA. And now as a thank you, you are forcing us to buy a Premium subscription for all products (in our case 3: Jira, Jira SM and Confluence) where we configured custom domains or you will revert them all back?
Really? Premium for a feature that is just standard in almost any other SaaS platform? And that is not even exactly what was asked for? No shame?
I personally think the rumors about Jira going EOL might be true with features like this being introduced this late and this broken. I just hope Atlassian will let us know publicly. I'm tired of hearing about Atlassian products being EOL through the grapevine without much notice.
We’ve heard your feedback and understand
It's clear you haven't truly grasped the severity of the issue. Saying you 'understand' feels dismissive and superficial. We need more than platitudes; we demand a substantial acknowledgment and actionable steps to address these concerns.
When will you actually offer the custom domain that was original requested over 10 years ago ? Never?
you are just going to ignore the original request and launch something no one asked for with 2 subdomains ?
Who wants that?? Most pathetic is that you seem to think this failure to deliver is a "Premium" feature 🙄
"We know many of you have given feedback about custom domains in the past. If you have additional feedback, we welcome you to share your candid feedback and concerns. We’ll be listening!" and then we will be ignoring all of it , close the ticket and pretend we solved it . Then we will ask you to make another request, and 10+ later we will kill that too
Hi everyone,
My name is Moinak Chatterjee and I’m a Senior Group Product Manager at Atlassian. We have a few important updates on custom domains.
Custom domains for Jira and Confluence
Custom domains are now generally available for Jira and will become generally available for Confluence starting in Q3. Custom domains for both Jira and Confluence will be available on Premium and Enterprise cloud plans. The rollout for Jira started today and will continue gradually over the next two weeks.
Custom domains are an administrative capability that allow organizations to use their own domain name to host Atlassian products. For example, using go.jira.acme.com instead of acme.atlassian.net. Using a customer-branded URL instead of an Atlassian-branded URL helps make sites more discoverable, accessible, and uniquely yours, since they’re based on the organization’s domain rather than Atlassian’s. Custom domains join the family of advanced administrative capabilities that are the foundations of our Premium offering and are also included in Enterprise plans, alongside features like sandbox and release tracks.
Custom domains for Jira Service Management help centers
For Jira Service Management (JSM) help centers, discoverability and branding are of the utmost importance so that your customers can get the help they need as quickly as possible. Custom domains for JSM help centers enable better customer service rather than better administration, which is why they will continue to be available on all paid cloud plans.
Getting started with custom domains
If you’re ready to get started with custom domains for Jira, follow these instructions. We will provide an update on this post when custom domains for Confluence become generally available.
If you are not already using a Premium license(s), you will need to upgrade to Cloud Premium to enable custom domains for Jira or Confluence. If you’re also looking for advanced scale, security & compliance, analytics, and support, we recommend you evaluate the Cloud Enterprise plan.
URL redirects for even more flexibility
We’ve heard your feedback and understand that many of you are looking for more flexibility in how you configure custom domains, which is why we also support URL redirects.
In designing the custom domains solution, we’ve been intentional about balancing security, customization, and open collaboration. Having a two-level domain plays a critical role in making our solution resilient to potential man-in-the-middle (MITM) attacks. At this point, we do not have plans to revisit the two-level subdomain construct, but customers who would like to use a shorter URL can set up a URL redirect. If you choose to use a redirect, you can create links with a shorter, fully customized base URL that redirects your users to the full URL.
What’s next?
Custom domains for Jira and Jira Service Management are generally available today. Custom domains for Confluence will become generally available in Q3. Therefore, we will close this ticket 30 days after Confluence custom domains become generally available. This will give you time to use this ticket to ask questions about how to use and access custom domains. After that time, we ask that you raise a support ticket with any questions.
We know many of you have given feedback about custom domains in the past. If you have additional feedback, we welcome you to share your candid feedback and concerns. We’ll be listening! But as a way to keep the dialogue productive, please note that we will prioritize addressing comments related to the functionality of custom domains and how to use them.
Best,
Moinak Chatterjee
Senior Group Product Manager, Atlassian
Wait so... is Custom domains widely released for Confluence? On the roadmap it says it has been released in Q2 2024? 1a3fac5bf2ee
Atlassian, you need to update your core values on your website. Based on this ticket, you haven't updated this one recently:
Don’t #@!%
the customerCustomers are our lifeblood. Without happy customers, we’re doomed. So considering the customer perspective - collectively, not just a handful - comes first.
The chances of getting a response from this company seem even slimmer than coaxing words from a stone, especially as their silence echoes the hollow ring of their greed. Each attempt to reach out is met with indifference, as they seem solely focused on lining their pockets, leaving genuine concerns unanswered. It's a stark reminder of their priority: profit over people.
I just want to make sure that custom domains are also offered for the standard cloud license and not just for Premium and Enterprise. Can I read something about this somewhere?
Regards,
Thomas
My suspicion is that they made a huge mistake in their Cloud architecture 15 years ago. With other vendors (SFDC Zendesk, for example), you have your cloud instance, and your users are associated only with your instance. Atlassian decided that users should be Atlassian Cloud users, who are authorized to access instances as owners of those instances see fit. They sort of took the AOL/Prodigy route (if you are old enough to remember the very early Internet before WWW).
almost 13 years in .. and Atlassian still completely ignoring the scope of this task, amazing. Will we ever get the custom domains this task was about? Maybe in 2027 or am I being to optimistic now 🙄
Oh great, they're giving us "URL redirects", which we didn't ask for, instead of what we actually asked for.
I am just sitting an waiting to see, if we ever will be able to migrate our OnPrem Jira to the cloud unter our own domain. It is a matter of trust and integration for us. It got quite entertaining here.
https://www.jetbrains.com/help/youtrack/cloud/domain-settings.html#use-custom-domain-name
If you have a registered domain — or plan to get one, you can configure your YouTrack Cloud instance to use your custom domain name. Instead of using yourcompany.youtrack.cloud or yourcompany.myjetbrains.com/youtrack, your YouTrack instance becomes available at yourcompany.com or youtrack.yourcompany.com.
When you change your base URL to use a custom domain, YouTrack automatically generates an SSL certificate and the corresponding private key. The certificate is signed by the Let's Encrypt certificate authority (CA). This certificate enable secure access over HTTPS to your YouTrack Cloud installation.