Hello Kate,
Welcome to Atlassian Community!
Next-gen are independent projects, so you can only move tickets, other things like custom fields, active sprints won’t be moved. Also, the project key won’t be moved, the tickets will have the project key of the new project.
Things to keep in mind if you migrate from classic to next-gen
Next-gen projects and classic projects are technically quite different. Here's a few things to consider when you migrate from a classic software project to a next-gen software project:
- Active sprints: Sprints in progress in your classic project won't move to your next-gen project. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project.
- Epic links: Links between epics and other issues (Story, Bugs, Tasks, etc...) in your classic project won't exist in your next-gen project. The issues themselves will still exist, but the links between them won't.
- Custom fields: These must be recreated in your new next-gen project.
- Story points estimation: This data will be lost, however you'll be able to start using story points estimation by enabling the Estimation feature in your next-gen project.
- Reports: Data for your project's Velocity report won't be saved. The Velocity report will show that no points were completed in past sprints.
- Report history: All reporting history is lost in this migration process. The Burnup report and Velocity report won't be migrated.
- Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue keys.
You can find all the details on the documentation below:
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.