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,415,378
Community Members
 
Community Events
170
Community Groups

Company is looking to create a separate instance for all Service Desk projects

My company has been looking into way to cleanup our Jira instance. We are currently at 70+ software projects and 5 service desk projects. One of the ideas that is always brought up is to move all of the service desk projects to a new instance (eg. company-service.atlassian.com).

I know there can be complications in terms of user licensing (Double licensing, increased cost) and being able to move issues across areas. 

I would appreciate input from the community on possible solutions and best practices. 

1 comment

Dirk Ronsmans Community Leader Sep 20, 2022

Hi @Max Orejola ,

Could you elaborate a bit on why you would need to move the projects in to seperate instances?

  • Are they supporting different products/services?
  • Is the customer base different?
  • Are the administrators for these projects different users?

You mention double costs so the agents supporting the projects would mostly be the same I guess?

In general, there is no reason to split them in to multiple instances. 99% of the things can be covered by permission schemes, issue level security, non-shared workflows, correct division of the customers, ... etc... 

So I'd really love to learn more why you really wish to split them in to multiple instances instead of keeping them together in a single one?

Like # people like this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events