Details
-
Suggestion
-
Status: Future Consideration (View Workflow)
-
Resolution: Unresolved
-
None
-
833
-
63
-
Description
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
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.
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.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-38229 Make it possible to use service desk in combination with subdomains
- Closed
-
JSDSERVER-1588 JIRA Service Desk have standalone Base URL different with JIRA
- Closed
-
JSDSERVER-4556 different base URL for servicedesk
- Closed
-
JSDSERVER-4794 Make it possible to use service desk in combination with subdomains
- Closed
-
JSDSERVER-6518 Enable internet access only to the Customer Portal.
- Closed
-
JSDSERVER-373 Domain Masking for customer portals please!
- Gathering Interest
- is incorporated by
-
JSDSERVER-5910 SDS email notifications should use Customer Portal URL instead of JIRA's Base URL
- Gathering Interest
- is related to
-
JSDSERVER-1627 Create ability to customize the Customer Portal URL in JIRA ServiceDesk
- Gathering Interest
- relates to
-
JSDSERVER-1588 JIRA Service Desk have standalone Base URL different with JIRA
- Closed
-
JSDCLOUD-513 Make it possible to use service desk in combination with subdomains
- Gathering Interest
- was cloned as
-
JSDSERVER-4794 Make it possible to use service desk in combination with subdomains
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...