• 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.

      N/A

            [AX-662] Allow custom domains for Cloud apps

            Pinned comments

            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

            Moinak Chatterjee (Inactive) added a comment - - edited 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

            John Hooper added a comment - 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

            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.

            Klaus Aengenvoort added a comment - 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.

            Will added a comment -

            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.

            Will added a comment - 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.

            Woojin Kim added a comment -

            https://6999.woojinkim.org/

            Thank you for everything.

            Woojin Kim added a comment - https://6999.woojinkim.org/ Thank you for everything.

            "comments will not be monitored" hahaha

            Do you really read the comments?

            Jaime Rodríguez Capote added a comment - "comments will not be monitored" hahaha Do you really read the comments?

            Wayne R added a comment -

            The resolution has mistakenly been set to 'Fixed'

            Wayne R added a comment - 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.

            John Hooper added a comment - 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.

            Sumit Gaur added a comment - - edited

            There should be something similar for confluence as well :  Jira Exit Interview

            #sattire

            Sumit Gaur added a comment - - edited There should be something similar for confluence as well :  Jira Exit Interview #sattire

            TestBot05 added a comment -

            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

            TestBot05 added a comment - 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

            Woojin Kim added a comment -

            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.

            Woojin Kim added a comment - 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

            John Hooper added a comment - 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

              1a3fac5bf2ee Joshua W.
              mhunter Matthew Hunter
              Votes:
              7602 Vote for this issue
              Watchers:
              2869 Start watching this issue

                Created:
                Updated:
                Resolved: