Thank you everyone who has voted or commented on this suggestion. Apologies for allowing this issue to remain open for a period of time without a clear update.
We've assessed this request and how it may positively impact our broad enterprise customer base. After initial analysis we have decided that we may not include this in our short-medium term roadmap. However, we’re not closing the ticket at this time in order to garner broader interest for this feature. I understand this may seem disappointing, but we believe it’s important for us to be open, transparent and honest with our customers.
In the mean time we’ve been busy and have recently released Priorities per project, Approval visibility and also addressed the #1 JAC issue of disabling account verification emails.
We will definitely post an update if we prioritize this feature earlier.
Thank you for your support.
— Jira Service Desk Team
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.
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.