Atlassian recently released a new type of project given the rather boring title of “next-gen”. Here is a snazzy
video which introduces this new project type: https://www.youtube.com/watch?v=PQa3NFB_LRg&list=PLaD4FvsFdarR69HESUlY4IC7ae5k5znYp&index=1
The primary new features of this project type are:
- An overhauled configuration experience that makes Jira faster and easier to set up
- New boards that allow you to mix and match the best features of Scrum and Kanban
- A new roadmap that improves your ability to plan long-term and share your plans with stakeholders (This would be a big win for us and is the primary reason we’re interested in moving to a next-gen project)
A more detailed list of features and difference with the current project types can be found here.
Unfortunately, this is not something that can just be enabled for existing projects, a new next-gen project must be created and then the classic project is migrated over to the next-gen project. While this can be somewhat painless (the process is detailed here), there are a few significant caveats to the migration process:
- Epic links and issue links: Any issue links in your classic project will not exist in your next-gen project. The issues themselves will still exist, but the links between them won’t.
- Subtasks: All subtasks will be lost in this migration process.
- 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.
The loss of Epic to Issue links and Story Points Estimations seems like a significant roadblock to us being able to perform this migration, as we have invested significantly in those features. However, I would love to hear if anyone has any ideas how we could work around this.