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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,628
Community Members
 
Community Events
176
Community Groups

Multiple service desk projects vs single service desk project

Both the company I work for and I myself are new to Jira. We're using service desk cloud, because we're a fairly small company. When I started we only had 2 service desk projects, one for IT and one for client support. But now we have a client that we provide IaaS for that needs to have their own service desk project. Basically they don't want any of their competitors to be able to see their offerings. Since we're on the cloud version we really can't limit the requests that a customer can see in the customer portal unless we create a separate project for them.

The IT group who will be handling most of the IaaS support does not like the idea of needing to monitor 2 projects (and potentially more if we get any other clients with the same requirement). We're getting around this by cloning issues from the client's project into our IT project, but it hasn't been easy to set this up and the number of automation rules has the potential to get pretty big if we add more projects like this.

I'd like to know if the more experienced Jira admins out there have any input on this. Is it that much more work tracking issues in multiple projects? Or would it be better to keep funneling them into 1 project so IT can pay attention to the main project while one person makes sure nothing is getting dropped in the other project?

0 comments

Comment

Log in or Sign up to comment