I find some features missing in Next-Gen, like swimlanes.
I am also worried that i will miss on new features if i choose "classic" now.
Is there going to be a transition from a classic project to the next-gen project once they are on parity with the features?
Welcome to Atlassian Community!
There are no plans in removing Classic projects in Jira. What is changing now is the new issue view that will be applied to Classic projects as well, but it won’t affect any functionality.
You can safely use Classic projects to use the features that are not available in the next-gen yet.
Please, vote and watch the feature request below to receive updates of when swimlanes will be implemented in next-gen:
If you have any other questions regarding this matter, please let us know.
There are some features that may be added, like the Roadmap that was a highly requested feature. It will depend on votes and comments on the features.
If there is some specific feature from next-gen that you need, please, feel free to raise a feature request on jira.atlassian.com (project JSWCLOUD) adding more details about why this is important for your environment.
If i understood you correctly, classic projects and next-gen projects will stay for good in the future.
May i suggest a transition from "Classic Projects" to "Next-Gen Projects" to be implemented sometimes in the future. The goal would be if there are some features added to next-gen in the future Jira users would be able to move their issues and project state to the next-gen project type. This transition would be a change of type for an already existing project.
I want to suggest this because there are features that are not available in Classic right now and i will create my project as a Classic one not to wait for swimlanes, but i might want to change the project type when new features come.
If I understood you correctly, classic projects and next-gen projects will stay for good in the future.
Yes, there are no plans in removing classic projects. Classic projects are more complete and complex when it comes to configuration and permissions and it’s possible to share workflows and custom fields between projects, for example, something that next-gen doesn’t have because it’s an independent type of project.
There is a feature suggesting a migration tool for classic to next-gen:
For more details about what data is lost when migrating from one project type to another, please check the documentation below:
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