Best way to setup service desk for multiple products support

What is the best practice setting up service dest for multiple products?

We decided to create a separate project for every product.

Afterwards we discovered that support email has to be diferent for each project.


So our customers will endup with:


That sucks...


What I'd like to create is some sort of global inbox with some automatic routing to new projects.


For example:

1. If possible to detect the product move ticket to a dedicated project

2. if not possible to detect leave for manual decission -> move to dedicated project

3. Have separate hipchat channels for each project

4. The customer should be able to communicate via all the time while using email channel.




Is it possible to split this that way or its better to label issues and create Queues for each product?


Best Regards


1 answer

Hi Przemyslaw,

I'm currently facing the same issue. Did you manage to find a work-around, or alternative solution?



Hi @Seamus Kieran


Unfortunately, no.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 13, 2018 in Jira Service Desk

Jira Service Desk – Don’t be afraid, the journey begins with curiosity! more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...

36,684 views 13 39
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