The following information only applies to next-gen projects
If you're unsure what type project you need help with, check the bottom of your project sidebar. If you see the Give feedback and Learn more menu items, you're in a next-gen project. If you don't, you're in a classic project.
By default, anyone with product access to Jira Software can create a next-gen software project. Unlike classic projects, next-gen projects don't share their configuration with any other project on your Jira site. And, you make updates without worrying about affecting other software projects on your Jira site.
With next-gen software projects, anyone can manage their own work, their team’s work, and their working processes, without having to reach out to a Jira admin for help.
In this section:- Create, edit, and delete next-gen projects
- Add or remove people who can view, work on, or administer your next-gen project
- Manage how people access your next-gen project
- Set up issue types in next-gen projects
- Customize an issue's fields in next-gen projects
- Manage Atlassian Marketplace apps in next-gen projects
Jira administrators can control who's allowed to create a next-gen project in their global permissions settings. Learn more about global permissions.
If you want to migrate an existing classic project to a next-gen project, or the other way around, check out our tutorial on converting a project to a different template or type.
Here’s what’s different in your next-gen project:
Issue types. You can define your team’s work by creating issue types unique to your team’s working process. These issue types have their own workflows, which are unique to your project. You can quickly update or change the fields your team uses to describe each type of work.
Fields. Fields you create for your issue types are available to every issue type in your project. They’re unique to your project only. You can still use them to filter for issues across your Jira site or in dashboard gadgets. But, they belong solely to your project.
Access and permissions. Next-gen projects prioritize access based on project roles that are unique to your project. You can assign individual people and groups to roles in your project to control their access.
Features. You can experiment with different working styles by enabling and disabling agile features, like backlogs, sprints, estimations, or releases and versions. Use as many as your team needs, whenever they need them, and turn off the rest to help you focus.