Working with next-gen software projects

Next-gen projects are the newest projects in Jira Software. They're perfect for small, autonomous teams that want to quickly jump in and get started, without the need for a Jira admin. We're building next-gen Jira Software from the ground up, so it doesn't yet have all the features that our classic Jira Software does.

You can keep track of what we're working on next at our Jira Software Cloud public roadmap.

NOTE: To use a next-gen board, you need to create a next-gen Scrum or Kanban project. You cannot add a next-gen board to a classic Scrum or Kanban project.

Get started with next-gen

Explore the basics of next-gen boards to help you get started on your next big project. Learn more

Get your team involved

Invite your team to your next-gen board so you can start collaborating. Learn more

Manage epics in next-gen projects

Track high-level work using epics, and add and remove stories to epics to manage work at multiple levels.  Learn more.

Manage subtasks in next-gen projects

Break down stories, bugs, and tasks into more granular steps. Learn more.

Add rules to your next-gen board

Automatically assign issues or update their fields when you move them across the columns of your board. Learn more

Enable agile features

Next-gen boards include optional agile features. Switch on/off features to tailor the board to your team's needs. Learn more

Integrate with other tools

Make your project even more powerful by linking it with tools like Bitbucket. Learn more

Manage your next-gen project

Learn about configuring issue types, fields, and other settings for your next-gen project. Learn more

 Classic vs next-gen Jira Software - What's the difference?

Jira Software's classic experience has the power and functionality that Jira is known for. It has a steep learning curve, but a huge number of options for planning, tracking, and reporting on your team's work. 

Next-gen projects provide a streamlined experience, are easier to use, and quicker to set up than classic projects. They don't require any setup or configuration from a Jira admin, so they're perfect for teams who want to work quickly and independently.


Advanced and flexible configuration, which can be shared across projects.

To learn more, see Managing project permissionsIssue field configuration schemesIssue type schemes and Issue workflow schemes.

Basic, streamlined configuration.

Configurations are per-project. Settings such as issue types and fields can't be copied over to other projects.

AdministrationStandardized project configuration. Configuration objects (like issue types, fields, and workflows) are globally reusable across your Jira site.Teams can configure project settings without impacting other projects.



Advanced RoadmapsPremium only(error)
  • Velocity
  • Burndown
  • Sprint report

And dozens more - see the full list.

  • Velocity
  • Burnup
  • Cumulative flow diagram
  • Sprint burndown

More coming soon

EstimationStory points and time estimationStory points only
Time tracking(tick)(tick)
Dev tools integration(tick)(tick)

Releases and version management

Parallel sprints(tick)(error)
Card layout customization(tick)(error)
Custom fields



Detailed permissions


Detailed and granular project permissions. Get more specific about who can do what in your project.


Simple access permissions only. Choose if a project can be accessed by the team, or by everyone on your Jira site.

Quick Filters



Default filters are included such as Assignee, Label, and Epic; but additional JQL filters can't be created.

Marketplace apps



Note: Apps that make project configurations (eg; new issue types or new statuses) won't work in next-gen.

Last modified on Aug 18, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.