Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-513

Make it possible to use service desk in combination with subdomains

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

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      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.

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

            Hi all, 

            Just an FYI that this feature request can now be solved using RefinedWiki's app, RefinedSites for Jira Service Desk We released the new custom domains feature just two weeks ago. Here is a blog post to tell you more: https://www.refinedwiki.com/blog/your-support-site-your-custom-domain-for-jira-service-desk-cloud/

            Genevieve (Refined Partner Manager) added a comment - Hi all,  Just an FYI that this feature request can now be solved using RefinedWiki's app, RefinedSites for Jira Service Desk We released the new custom domains feature just two weeks ago. Here is a blog post to tell you more: https://www.refinedwiki.com/blog/your-support-site-your-custom-domain-for-jira-service-desk-cloud/

             +1

            We need this on cloud

            Jean Luchtenberg added a comment -  +1 We need this on cloud

            Yeah, that's crazy that this has been open more than two years.  I'm sure there's a lot of internal code that references the single base-url.  But there's no reason it can't be done as a piecewise rollout that one component at a time can use an alternative base-url.

             

             

            Mark Murawski added a comment - Yeah, that's crazy that this has been open more than two years.  I'm sure there's a lot of internal code that references the single base-url.  But there's no reason it can't be done as a piecewise rollout that one component at a time can use an alternative base-url.    

            It's a shame to see Atlassian is so slow addressing basic feature. In IMHO this feature should be part of v1.0  and yet 2+ years since was requested nothing changed. 

            Gregor Novak added a comment - It's a shame to see Atlassian is so slow addressing basic feature. In IMHO this feature should be part of v1.0  and yet 2+ years since was requested nothing changed. 

            Is there a process to submit bounties for features?  I'm sure we could crowd fund a decent bounty to expedite this majorly needed feature.

            Mark Murawski added a comment - Is there a process to submit bounties for features?  I'm sure we could crowd fund a decent bounty to expedite this majorly needed feature.

            We definitely need the ability to have a subdomain on a per service desk basis.  We're growing and supporting several franchises and we absolutely must be able to brand each service desk individually.

            Mark Murawski added a comment - We definitely need the ability to have a subdomain on a per service desk basis.  We're growing and supporting several franchises and we absolutely must be able to brand each service desk individually.

            We have already decided to go with another provider – or build our own tool – due to the lack of this essential feature. 

            We tried many of the proposed solutions sent to us by JSD support – spent a lot of time trying them out – and none of them worked.  And honestly, a lot of the support we received was half-hearted.

            We like JIRA but need to move on if they can't meet the important needs of customers.

            Michael Woffenden added a comment - We have already decided to go with another provider – or build our own tool – due to the lack of this essential feature.  We tried many of the proposed solutions sent to us by JSD support – spent a lot of time trying them out – and none of them worked.  And honestly, a lot of the support we received was half-hearted. We like JIRA but need to move on if they can't meet the important needs of customers.

            Bill Weils added a comment -

            Echo this all around.  When providing Customer facing service – through individual customer accessible portals - this feature is an extreme must have.

            The opportunity to provide service to a customer via "https://{customername}.{mydomainname}.com — and then have the rest of the Service Desk cloud URL metadata suppressed/hidden from the customer would be huge.   

            On a security/information sensitivity concern - the ability for some to "hack at" the URL and discover various customers (providing we have placed a customer brand/logo) on the entry page – is highly detrimental to continuing service with the Atlassian Service Desk (Cloud) offering.

            Atlassian – please make a comment – give us some perspective on roadmap.  We believe in the service, but elements like this will eventually sink your business as we move to another provider with better features (regardless of their pricing).......

            Cheers.

            Bill Weils added a comment - Echo this all around.  When providing Customer facing service – through individual customer accessible portals - this feature is an extreme must have. The opportunity to provide service to a customer via "https://{customername}.{mydomainname}.com — and then have the rest of the Service Desk cloud URL metadata suppressed/hidden from the customer would be huge.    On a security/information sensitivity concern - the ability for some to "hack at" the URL and discover various customers (providing we have placed a customer brand/logo) on the entry page – is highly detrimental to continuing service with the Atlassian Service Desk (Cloud) offering. Atlassian – please make a comment – give us some perspective on roadmap.  We believe in the service, but elements like this will eventually sink your business as we move to another provider with better features (regardless of their pricing)....... Cheers.

            Totally agree! This is an important feature!

            Daniel Kemen added a comment - Totally agree! This is an important feature!

            Definitely need this feature as our support portal is customer facing.  Please make it a priority to allow a friendly URL such as support.mydomain.com.

            Michael Woffenden added a comment - Definitely need this feature as our support portal is customer facing.  Please make it a priority to allow a friendly URL such as support.mydomain.com .

              a1217920d496 Ash Young
              aaa69d7d-d057-4df5-bc55-2263b1aa7daf Deleted Account (Inactive)
              Votes:
              304 Vote for this issue
              Watchers:
              176 Start watching this issue

                Created:
                Updated: