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?
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.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events