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


0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

1,236 views 2 14
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