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

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

How do you manage multiple service desk portals? (solved) Edited

We have several projects that use the next-gen service desk.  And a few customers that work on several of these projects. 

The NextGen Service Desk portals have a URL like:  https://xxx.atlassian.net/servicedesk/customer/portal/13

Based on the URL it's impossible to see to which project it relates.  For example: it would be a lot clearer if this would at least use the project key like: https://xxx.atlassian.net/servicedesk/customer/portal/PXD

But this is not possible.  So, now they have to remember: nr 13 is for this project A, number 5 is for project B, number 21 is for project X.   This is not user-friendly at all and often issues are created in the wrong portal. 

 

How do other people manage this? 

 

Right now, the only option I see it to publish a HTML list somewhere that lists a link to all our JIRA portals with the related project name.  But this feels so redundant and the extra step is annoying for the users. 

2 comments

Dirk Ronsmans Community Leader Jul 15, 2020

@lies 

Perhaps this is something different with next gen but I don't think so.

If you go to:

http://xxx.atlassian.net/servicedesk/customer/portals

you should just see all the portals they have access too with the proper portal/project name.

Like lies likes this

yes! thank you!

this is exactly what i needed :-)

Dirk Ronsmans Community Leader Jul 15, 2020

@lies 

for future reference, this is called the Help Center and it lists all the portals you have browse project permissions for :)

Like lies likes this

@lies I agree with you, it would make much more sense to replace the customer portal ID by the project key (friendly URL).

Dirk Ronsmans Community Leader Jul 15, 2020

Well yes and no, you can always change the KEY afterwards but the id stays the same.

So from the point of view where everything continues to work it makes sense to use an id.

Comment

Log in or Sign up to comment
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