Updating Your Apps: A Developer’s Guide to the New Jira Field Schemes API

[#1]

👋 Hello Partners!

If your app manages field visibility, requirements, or project configurations in Jira Cloud, it’s time to look at the new Field Schemes API. We are moving from the legacy two-tier model (Field Configurations + Schemes) to a streamlined, single-tier Field Scheme model.

Why the change?
The new model simplifies how fields are managed by associating them directly with schemes. This reduces the complexity of your API calls and introduces powerful bulk operations.

Key Technical Shifts for Your App:

• From Two-Tier to Single-Tier: You no longer need to create a configuration and then map it to a scheme. Everything—from field parameters to project assignments—is now handled within the Field Scheme object.

• Visibility via Association: The isHidden flag is gone. To "hide" a field, your app should now simply remove the field association from the scheme using DELETE /config/fieldschemes/fields.

• Bulk Updates: The new API is built for scale. You can now update parameters or associations across multiple schemes in a single request.

Looking for the full technical breakdown?
For a comprehensive, step-by-step mapping of every legacy endpoint and detailed behavioural changes, please refer to our https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/From-Field-Configurations-to-Field-Schemes-Migration-Guide-for/ba-p/3245633.