What are field configurations and field configuration schemes?

This page refers to fields that can be used in any project, and requires Jira administrator permission.

Fields in team-managed projects

 

As administrator, you can group fields in your site into field configurations for easy management. You can then use these in Field configuration schemes to make fields appear in specific projects and work types.

We're making some big changes to Fields in Jira. See our update in the Jira Admin Community space.

Field configuration and scheme size limits are coming in February 2026

Jira will limit the number of fields and work types that can be used in a project to improve performance and reliability of large sites from February 2026.

Field configurations will be capped at 700 fields. Schemes will be capped at 150 work types per scheme.

To do this, the steps are as follows:

Let’s give this some real world context: the development teams in your organization require unique fields as part of their work processes that no other teams do. They also require a slightly different set of fields based on the work type – i.e. Bugs require a field that Tasks do not.

Once all of the fields have been created, you’d first make a separate field configuration for Bug and Task work items that contains the fields you want to appear on each.

You’d then add those configurations to a field configuration scheme, and associate it to their development projects. Then, in the individual projects, you would apply the field configurations from the scheme to the individual work types – Bug and Task.

After this, you’ll have a standardized group of fields that can be applied at the individual work type levels based on the project’s needs.

Still need help?

The Atlassian Community is here for you.