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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Retaining the same project key and migrating a JIRA project to next gen project

Hi All,

My team follows a naming convention in our documentation and bitbucket branch names that include the the JIRA project key to have a reference  to the project. 

When creating a new next gen project, we can't have the same PROJECT KEY, so can you please suggest what can be done?

Also I did read few other posts and have looks like there is no straightforward way to bulk migrate issues, please let me know if there is a way, any question or JIRA ticket that I can follow?

1 answer

1 accepted

0 votes
Answer accepted

Hi @Sai Pravesh ,

You can refer the steps for migrating the project type.

Later you can delete or change project old project and update the new project Key.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events