Public JIRA + Service Desk = confusion (JSDSERVER-1367)

We have a public read-only JIRA for showing customers bugs/improvements in our product.

We also have Service Desk and use the customer portal to allow them to create service desk issues.

The problem is the customer can see the issues in public JIRA when they are not logged in to JIRA Service Desk, but once they login to JIRA Service Desk, they can't no longer view the issues in the public JIRA. Keeps on getting redirected to the JIRA Service Desk.

Our "work around" is to tell customers to use two different browsers - Chrome for Service Desk and Edge or Firefox for our JIRA. This is not ideal as we often link JIRA issues in comments for Service Desk issues, so there is never ending confusion by our customers who are confused and frustrated with not being able to access the JIRA when logged into Service Desk.

This was logged as JSDSERVER-1367 over 2 and a half years ago, and as seen in the comments affects many people.

Is there a better work-around? Will this ever be fixed?

1 answer

0 votes

Hi Mike,

Sorry to hear of the problems caused here.   There are a couple of work-arounds I am aware of that might help here:

  1. You could follow the steps in How to customize the customer portal URL in JIRA Service Desk.  By doing so you could set the customer portal to be on a separate DNS domain name than the main JIRA site where these customers are not able to login and in turn are expected to be anonymous viewers of the site.  (ie for the JSD portal and something like for your public bug tracker).
  2. Alternative to those steps, would be to have different JIRA installations for your Service Desk project and your JIRA Software project.  Same idea though as above though, just a different way to accomplish this when on different JIRA installations.  If each JIRA instance has a different site URL, the users logins would stay with the site they are visiting. 

I think the first method is easier to do overall, because the second method would require a new install of JIRA, and possible project/data migrations.   Also to separate the instances can lose some advantages of licensing (such as if you have a JIRA Software and a Service Desk license on the same JIRA instance, you can easily have those Software users make internal comments to Service Desk issues.  Whereas if you separate the installations, those users can't do that)

Thankyou Andy for your reply and guidance.

I've looked at what I need to do with your recommended suggestion to use a different DNS domain name for the customer portal- it looks promising.

I'll try that and report back if I had success - at which point you may want to consider adding a comment to JSDSERVER-1367 indicating this is a possible solution, and also update How to customize the customer portal URL in JIRA Service Desk to include information that it may be a workaround for JSDSERVER-1367, in order to save poor souls like myself Googling for solutions and not readily finding a solution.

Thanks again for your interest in my problem :)


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira Service Desk

What's new in Jira Service Desk Server: Introducing 4.0 & more - Feb 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...

385 views 1 1
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you