Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,551,839
Community Members
 
Community Events
184
Community Groups

What are the advantages of migrating multiple projects into one single project in jira?

sarvesh_4396
sarvesh_4396
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
May 03, 2023

Please give some point wise advantages of migrating multiple projects into one project in jira.

Answer
Watch
Like Catalin Nichita likes this
137 views

1 answer

2 votes
Alex Koxaras _Relational_
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
May 03, 2023

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.

Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
TAGS
AUG Leaders

Atlassian Community Events

See all events