Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-6999

Allow custom domains for Cloud apps

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      Problem

      With Cloud apps, domains are always of the form *.jira.com (for legacy Studio customers; no longer available) or *.atlassian.net (for any OnDemand/Cloud Customers). Customers are interested in the ability for them to use their own domain names, e.g. jira.example.com. 

      Atlassian Status Update - 4 November 2019

      Hi all,

      We recently published a blog documenting changes that are coming for app developers in the context of custom domains. We will be adding some new fields to the install payload to inform apps if an instance is associated with a custom domain name. For the most part we do not expect apps to need the information in these fields. It is provided for any cases where an app needs to render links, server side, using the custom domain.

      If you have any questions about supporting custom domains in your apps, please post them on our Developer Community forum thread on these changes.

      Thanks,

      Victoria
      Atlassian Product Management

      Atlassian Status Update - 3 October 2019

      Hi Everyone,

      This is a quick update - as mentioned in my previous message, we have presented a detailed talk on custom domains at our Atlas Camp in Vienna (Atlassian Developer Conference). The talk covers the impact of custom domains on APIs and required changes for apps and integrations. The video recording and presentation slides are available via this link here.

      You may have noticed that the status of this ticket has recently changed to ‘future consideration.' This was an unintentional side effect of us making changes to the workflow for this Jira project. Our teams are actively working on this feature and I have updated our ticket to ‘in progress’ to reflect this.

      Thanks,
      Victoria
      Atlassian Product Management

      Atlassian Status Update - 9 September 2019

      Hi Everyone,

      This is a product update, we’re now in active development for a number of the key streams required to implement custom domains.

      We’re also working on identifying the impact of custom domains on ecosystem apps and integrations. We’ll be talking in detail about custom domains at our upcoming Atlas Camp in Vienna (Atlassian Developer Conference). Shortly after, we’ll share more information on developer.atlassian.com regarding the impact of custom domains on APIs and required changes for apps and integrations.

      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.

      As we continue our progress on this feature, we’ll be providing further updates including bringing this feature to Confluence Cloud Premium. We’ll also be reaching out to customers to refine our solution and ensure we meet your needs.

      Thanks,
      Victoria
      Atlassian Product Management

      Atlassian Status Update - 11 April 2019

      Hi everyone

      So... It's been well over 6 months since the last update. Definitely not what I was planning. However - attendees at Atlassian Summit in Las Vegas currently would have heard that we've shipped the initial iteration of being able to rename an Atlassian Cloud site, which is the precursor to supporting custom domains for Jira and Confluence Cloud. Time for an update then, specifically to the three points I referenced previously:

      1. We've chosen our initial approach for managing the SSL certificate lifecycle, and this is in active development 
      2. We've continued our investigation into how user accounts should be handled for Jira and Confluence Cloud sites that have a custom domain configured. We have a good understanding of the work required to maintain account security in this scenario, and are now working through scheduling and logistics
      3. We've made a sizeable dent to the problems posed by CLOUD-7184, as referenced above - our Support team can now rename an Atlassian Cloud site, for eligible sites. Eligibility is determined by the Ecosystem apps installed, and whether they are compatible with the rename process. While there's still work to do to close this out fully, it also addresses a significant (not the full) amount of work required to support custom domains

      We're continuing to work through this internally, with efforts expected to ramp up over the next few months or so to finally get an initial iteration into customer hands. It's not quite the update everyone wants to read, but hopefully it's a demonstration of some progress. 

      Thank you again for your patience - I want to reiterate that there is a team of Atlassians continuing to work on this, and we're committed to knocking down the barriers to light this up. 

      Cheers
      Nuwan
      Atlassian Product Management

      We receive a lot of requests for new features and improvements, so if you'd like to better understand how we make roadmap decisions, please read: https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html

      Atlassian Status Update - 26 June 2018

      Hi everyone

      First things first - you're not shouting into the void. We truly appreciate all of the comments that come in on these two feature requests (CLOUD-6999 and CLOUD-7184) - they keep us honest, and are a valuable, sustained reminder of the importance of these capabilities to our customers. We definitely agree with all of you and, despite the silence on this ticket, have been working on these issues internally.

      So, what gives? Why is it taking us so long to get this done? There are a number of reasons, but here are the key ones:

      1. Secure hosted products for all customers. Serving Internet traffic over HTTP is no longer acceptable - we must support SSL for all connections to our products, including those accessible via a custom domain. We've seen a number of companies choose the LetsEncrypt route for securing traffic, and there are an increasing number of third-party offerings that could solve this problem for us. Managing the SSL certificate life-cycle through initial request, validation, deployment and renewal while delivering a comprehensive, supportable customer experience, is a significant body of work - one we take very seriously. We're continuing to evaluate options to provide a seamless and robust security offering, across both the LetsEncrypt and third-party options.
      2. Authentication. The last two years have seen the progressive rollout of a new Identity platform to Jira and Confluence. While the rollout of Atlassian accounts has enabled for single sign-on between these products, it has changed the way we need to think about custom domains and user account security. This is something we're taking the time to explore in depth, due to the significant impact that any user account issue would have on our customers. 
      3. Addressing invalidated assumptions. We need to address some fundamental assumptions in Jira & Confluence Cloud that no longer hold in our post-Vertigo world. There's no question as to the customer value this unlocks - we're working with the various teams involved to schedule the necessary effort to address this. 

      I had hoped that my next update (this one) to these tickets would be with something more concrete - that we had launched our beta program, or had a pilot program in place. Sadly, hindsight shows that my last update was overly optimistic. While I don't want to make that mistake again, I also appreciate that this update will undoubtedly frustrate watchers expecting a more meaningful Atlassian response. I'm expecting more brickbats than bouquets until we've delivered this, and rightly so.  

      If nothing else - please be reassured that we are listening, we understand the need to deliver this, and a group of passionate Atlassians are working in the background to get this into your hands. 

      Cheers
      Nuwan
      Atlassian Product Management

      We receive a lot of requests for new features and improvements, so if you'd like to better understand how we make roadmap decisions, please read: https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html

      Atlassian Status Update - 30 March 2017

      Hi everyone

      It's been far too long since our last update regarding custom domain support for JIRA and Confluence Cloud. That update referred to Cloud platform stability and improvements to our Identity-related capabilities (SSO, SAML to name a few) as key priorities for our Cloud platform. We've made headway in those areas since then, and I'm pleased thrilled to confirm that we now have a project underway to deliver custom domain support for JIRA and Confluence Cloud.

      To address some key points:

      • This will require site admins to verify ownership of their domain, something that we've recently introduced as part of the SAML rollout - you can read more on the domain verification process here
      • Based on the current domain claim process, we will only be able to assign a custom domain to a single site. We're looking at ways to remove this limitation in future releases
      • Custom domain support will also be progressively rolled out to existing customers over time. At this point we're targeting July-September 2017 for a private beta. As always, our roadmaps are subject to change.

      In the interests in full disclosure, custom domain support will one day form part of a Premium edition for Atlassian Cloud products at additional cost, along with SAML and other feature offerings. There will of course be no charge for participation in private and public beta programs. We're currently discussing what grandfathering options we can apply for beta participants.

      Please complete this form if you'd like to participate in our private beta. The form asks a few questions to help us understand intended usage in more detail, as well as registration details for the private beta. If eligible, you will receive an invitation email with next steps once we're ready to kick off the private beta.

      I'll update this ticket again once we have further progress updates, and more comprehensive documentation is available.

      Thanks again for your patience - we appreciate the significant level of community interest in this capability, as well as the frustration that this has generated to date. There are a number of Atlassians who keep a very close eye on this ticket, and we're all very excited to be able to offer a more concrete update to you, and finally start engaging in a meaningful fashion.

      Cheers
      Nuwan
      Atlassian Product Management

      We receive a lot of requests for new features and improvements, so if you'd like to better understand how we make roadmap decisions, please read: https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vli@atlassian.com Victoria Li
              Reporter:
              mhunter Matthew Hunter
              Votes:
              3855 Vote for this issue
              Watchers:
              1470 Start watching this issue

                Dates

                Created:
                Updated: