nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Separate URLs for new Service Desk

Emile Renaud

Hi,

We have an existing Service Desk Project with URL companyname.atlassian.net, we're in the process of setting up an additional Service Desk Project, but I'm unsure how to set a separate URL (differentcompanyname.atlassian.net) for this second project.

I've searched high and low but cannot find any tickets discussing this. Please advise.

Thanks

Accepted answers

Dirk Ronsmans

Hi @Emile Renaud ,

On cloud the url is linked to a whole instance (so not just a single project). If you have multiple projects they will have separate portals but those will be in the form of:

There is also a help center which will show the users all the "portals" they have access to under:

https://yourcompanyname.atlassian.net/servicedesk/customer/portals

If however you need multiple instance names that would be multiple instances/subscriptions to the platform but that also requires additional budget then and it would have a much larger impact than just having multiple projects.

If you do need some kind of different url you could set up your own domainname (on your own infrastructure/dns) and have redirects to the other portal url's

Is there a specific reason why it needs to be a different subdomain?

If you need to service multiple customers it would make more sense to have a single url with your company name and name the projects as the customer.

OR, you could have a single project and set up multiple organisations for the customers.

It depends a bit on your use-case

All comments

Dirk Ronsmans

Hi @Emile Renaud ,

On cloud the url is linked to a whole instance (so not just a single project). If you have multiple projects they will have separate portals but those will be in the form of:

There is also a help center which will show the users all the "portals" they have access to under:

https://yourcompanyname.atlassian.net/servicedesk/customer/portals

If you do need some kind of different url you could set up your own domainname (on your own infrastructure/dns) and have redirects to the other portal url's

Is there a specific reason why it needs to be a different subdomain?

If you need to service multiple customers it would make more sense to have a single url with your company name and name the projects as the customer.

OR, you could have a single project and set up multiple organisations for the customers.

It depends a bit on your use-case

Emile Renaud

Hi Dirk,

Thanks for your input. I'm going to review the above and revert to you incase I have more questions or comments.

Regards,

b6f9d4dd-5ba1-4a56-8ceb-4edf8b668073

Hi @Emile Renaud

thanks for the question, actually we are in need of same matter you search for too.

Hi @Dirk Ronsmans

You have asked Emile the reason; I would like to descripe our need and would like to obtain your opinion to shed some light on our problem.

In our company, we have serious numbers of people working on field and due to their working conditions and environment we have to present different sub-groups and / or simplified field to fill so they could easily and promptly raise service request.

Due above mentioned logic we are looking for establishing second portal page for employees working in the field.

we wonder if you could suggest something.

In advance thanks a lot.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management