Next-gen projects are:
Jira's next-gen projects simplify how admins and end-users set up their projects. They come with a re-imagined model for creating, editing and representing project settings.
In classic projects, Jira admins configure a project using schemes to map shared objects to projects, like issue types, workflows, fields, and permissions. While schemes maximize the ability to share configurations across multiple projects, they can be difficult to understand.
Over time, we've added additional layers of configuration to improve customization. But, these layers can make it more difficult for admins to learn and maintain their setup. We built next-gen projects to help fix this. They're easy to set up and will grow with more straight-forward customizations in the future.
Classic projects also leverage objects that exist only at a global level, across your entire Jira site. That makes it easy for Jira admins to push configuration changes across a bunch of projects. But conversely, end users are unable to manage configuration for their own projects. The burden of configuration falls entirely on Jira admins, making it a complex and time-consuming process to customize a project every time a new project or a new team comes to your Jira site.
With next-gen projects, we empower the project owners themselves to customize their projects based on their unique needs without bothering a Jira admin to help them. They can easily add or remove fields to their issue types, set up some interesting automated rules and more.
We know that organizations have multiple teams and projects with common workflows and standardized reporting. In the future, we will be working on making configuration reusable across different next-gen projects. For now, configuration is bounded by the project and fully controllable by project admins.
On the bottom of your project sidebar, there will be an icon with text "You're in a next-gen project", along with a Give feedback and a Learn more link.
Read more about the detailed differences at Classic and next-gen project templates in Jira Software Cloud
To find out what's shipped and what's coming for next-gen software projects, check out our public roadmap.
Next-gen projects represent the future of Jira. We added the most-needed, most-common project settings first. And, we're constantly adding additional settings based on your feedback.
Next-gen projects don't have schemes. Your next-gen project's setup objects – for example, its issue types and fields – are all contained within the project. Since these objects are no longer dumped in the pool of global objects on your Jira site, you don't need schemes!
Soon, we'll give you the ability to extract your next-gen project settings into their own template, and link two or more projects' settings together. If you need to share configurations across projects today, you might be happier with a classic project.
Jira admins can control which groups of users create next-gen projects using the Create independent projects global permission. Read more about global permissions.
You can add a new status directly on your board. Simply add a new column, and drag and drop it into the spot you want. Next-gen projects support neat, linear workflows at the moment. More workflow configuration is coming soon.
Rules replace advanced workflow configuration operations like post functions, validations, conditions. Currently, there are two rules available to next-gen software projects:
Learn about setting up lightweight workflow rules for your board at Add rules to your next-gen board.
Any project configuration or customization you do in a next-gen project is independent and only available for that project. If you need to share issue types and custom fields across multiple projects, you might be happier with a classic project.
Today, you can't reuse an issue type or status from one next-gen project in another next-gen project. In the future, we'll introduce project templates which allow you to save and share an entire project configuration (issue types, fields, workflow, and more). Other teams in your organization can use these templates as a quick starting place for their own next-gen projects, or you can link a few projects together to share their settings.
Yes! Most everything should work properly. But, we have borked a few things. If you're developing an app, learn what you need to know developing for next-gen projects.
Jira admins can create a classic project and move their next-gen project issues into the new, classic project. Read more about migrating from next-gen to classic projects.
If you're not a Jira admin, ask your Jira admin to do this for you.
Interested in what's coming next? Please visit the public roadmap
New to next-gen projects in Jira Software Cloud? Check out this guide to getting started with next-gen projects
Would like to know a lot more about next-gen? Watch the new Jira begins now