• 121
    • 63
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Atlassian Update – 28 Jan 2021

      Hi everyone,

      Thank you for your interest in this issue.

      This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

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

      We hope that you appreciate our candid and transparent communication. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

      To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

      Kind regards,

      Charlie

      Jira Service Management, Server & Data Center


      Currently it is not possible to use create a subdomain, f.e support.example.com and link this subdomain to the service desk url https://www.example.com/jira/servicedesk/customer/key.

      Workaround

      Use a Reverse Proxy or URL redirect service external from JIRA.

      Another workaround is described in How to customize customer portal URL in JIRA Service Desk Server

      • Please ensure you test this first on your test instance before you implement on your production.
      • Please also note that Atlassian does not support this customization.

            [JSDSERVER-513] Make it possible to use service desk in combination with subdomains

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

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

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

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

            mb added a comment -

            10 years and no progress

            mb added a comment - 10 years and no progress

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

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

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

            Falko Sieverding added a comment - Is there any update on this feature request? When will custom subdomains for Jira SD be implemented?

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

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

            Mark Murawski added a comment - There's still datacenter for onprem. Which means Atlassian is continuing to give the big FU-WeDontCare to people who are paying $42k+ a year for software. That's half a developer salary... they can't take 10-20 hours to develop custom domains? Come on...

            Hi,

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

            Martin

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

            Hi,

            I very doubt Atlassian will do anything about all those 5+ years old tickets pertinent to products that are soon going EOL They're going to force all customers to migrate to their Cloud products so it's probably more efficient and less frustrating to log features features there instead. Therefore, it's a bit pointless to leave further comments here - am unsubscribing as well as looking for alternative products that are open source and new key features can be added by community or do it myself within weeks or months but not years or never. Atlassian have proven over the past 8 years that they don't seem to care about what customers are saying and tend to stick to their own roadmap ignoring those who products are made for in the first place.

            Best,

            David

            David Sadowski added a comment - Hi, I very doubt Atlassian will do anything about all those 5+ years old tickets pertinent to products that are soon going EOL They're going to force all customers to migrate to their Cloud products so it's probably more efficient and less frustrating to log features features there instead. Therefore, it's a bit pointless to leave further comments here - am unsubscribing as well as looking for alternative products that are open source and new key features can be added by community or do it myself within weeks or months but not years or never. Atlassian have proven over the past 8 years that they don't seem to care about what customers are saying and tend to stick to their own roadmap ignoring those who products are made for in the first place. Best, David

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

            Tamas Bela added a comment - such an obvious disregard for customer needs is quite eloquent. nice job atlassian.

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

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

            Tech Support added a comment - This is such a simple feature to implement that I can't understand why they would frustrate people by not doing it. I have got around the problem by using IIS and ARR which means everyone is sent to my IIS server by and nice, easy to remember URL instead of directly Jira and I just reroute the requests. Not something I should have to maintain separately though!

              Unassigned Unassigned
              aaa69d7d-d057-4df5-bc55-2263b1aa7daf Deleted Account (Inactive)
              Votes:
              812 Vote for this issue
              Watchers:
              361 Start watching this issue

                Created:
                Updated: