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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.