Project configuration in classic and next-gen projects

When being set up, classic projects and next-gen projects work differently. In a nutshell, classic projects share configurations, whereas next-gen projects are all individual. For more details, read on.

In classic projects, fields are placed on screens. Then, screens, issue types, workflows, and statuses are mapped to schemes that are shared across all projects in your Jira instance.

Diagram to visualize the relationship between components shared across classic projects.

Next-gen projects have no schemes and screens — this makes project configuration a bit simpler. Each project then has its own fields, request types, workflows, and statuses: all of which can be configured for that particular project. This means that each project configuration must be configured individually - they can’t currently be shared across projects.

Diagram to show that fields, workflows, request types, and statuses in next-gen projects are individual to the project.

Additional Help

Ask the Community