Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira service desk CNAME

Hi!

Is it possible to change the portal link from the service desk to for example:

help.domainname.com using CNAME. I tried searching google for this answer but I had no luck doing so,

thank you in advance

1 answer

1 accepted

0 votes
Answer accepted

The service desk portals live under the base url given for your Jira system.

You could put a proxy in front of them with a different cname, but it will come back to using the base url quite quickly.

Hi Nic,

I know the portal link lives under the base url, but the problem with that is that you still have the ":port/portal/customer/number" which looks kinda ugly so that wouldn't be a solution to my question unfortunately.

Regards,

Menouer 

Daniel Eads Atlassian Team Oct 22, 2018

Hi Menouer,

Jira internally will not change the URLs for any hyperlinks it generates once you land in Service Desk. So Nic is correct; you can create something like "help.domain.com" using a reverse proxy, but once you actually arrive there, any links the user clicks will go someplace like "jira.domain.com/portal/customer/94".

I'm sorry if that's not the answer you're looking for! Unfortunately it's how the system works right now. There is an open feature request to allow custom URLs: JSDSERVER-1627 - I recommend watching and voting on that feature request. For more information about how Atlassian prioritizes feature requests made on jira.atlassian.com, check out this Community post.

Cheers,
Daniel

Hi Daniel,

JSDSERVER-1627 is not capturing the issue here.

JSDSERVER-513 is the correct ticket, and should be done, like zendesk and others. (it has the highest votes of any open issue)

This is a cumbersome workaround for something simple that shoud be in service desk.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you