You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Please give some point wise advantages of migrating multiple projects into one project in jira.
Hi @sarvesh_4396 and welcome to the community,
If the two projects have the same workflows, issue types, set of permissions etc, then this would be a very good reason in having your issues in one single container.
If your projects have different permissions, different roles and each role is doing something different and all of them can't co-exist under a single project, then it's best to use different containers.
In your case, and if you truly are interested in JSM, then different projects in your case would be if you had customers with different request types. A single service desk would be handy if you provided the same services to all your clients. Then you wouldn't have the need to have separate projects for separate clients.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.