· via dev.to (home feed)
Atlassian's Jira field schemes replace field configuration schemes in automatic Cloud migration
Atlassian automatically converted Jira Cloud sites from field configuration schemes to new field schemes; admins report orphaned schemes and old REST endpoints silently returning stale data.

The rollout
Atlassian has replaced Jira Cloud's field configurations and field configuration schemes with a single new object called a field scheme. According to a hands-on write-up on dev.to, general availability was announced on 10 June 2026; sites on the continuous release track were converted over the following weeks, and sites on bundled tracks were scheduled for 10 November 2026 — later than the September timing originally expected, as confirmed in a 20 October comment by Atlassian's Carol Low on the community FAQ. Admins got no say in the hour: Atlassian staff wrote in June that the conversion runs automatically in each site's maintenance window, and the only timing control was the site's release track.
What a field scheme replaces
Under the old model, two objects governed fields. A field configuration listed the fields and flagged each one as hidden, optional or required, and a field configuration scheme mapped the work types in a project to those configurations. A field scheme now does both jobs. Each space — Jira's current term for a project, though the REST API still says 'project' — uses exactly one field scheme, one scheme can serve many spaces, and a field missing from a scheme simply never appears in that space.
Two older mechanisms survive with narrower roles. Field contexts now set only a field's content, such as default values and dropdown options, and no longer hide fields from a space; every field also gains a global context that cannot be deleted. Screens and layouts remain the last checkpoint for visibility, so a field must be in the scheme and on a screen before users see it. Differences between work types — the term replacing 'issue type' — moved inside the scheme, where availability, requiredness and even the field description can be set per work type.
One behavior change to flag: newly created custom fields are not added to any scheme automatically and must be attached to the relevant schemes before they appear anywhere.
What the migration left behind
The dev.to write-up, based on a Jira Cloud test site on a Premium or Enterprise plan, inspected the results on 15 November 2026. The new Field schemes page listed 43 schemes across 59 company-managed spaces. Twenty-four schemes were linked to no space, and all were leftovers from deleted Jira Service Management spaces, holding between 69 and 233 fields each. Forty-two live spaces share the default scheme, and 11 team-managed spaces appear under no scheme at all. Jira refused to delete the default scheme and schemes still in use, but removed an orphan in a single call.
The legacy REST API is in a strange half-state. Read endpoints still answer with HTTP 200, but the counts no longer match the new model — 740 items in the old default configuration against 471 fields in the new default scheme. A query asking which scheme a space uses returned an empty list for all 70 spaces tested. Writes through the old API failed with a 404 against an identifier the old read endpoint still served, while the same change succeeded through the new API.
Atlassian's original announcement says the migration reads existing configurations, their linked spaces, fields, work types and field contexts, then builds schemes that keep today's fields visible — with a warning that sites may end up with more schemes, each tied to fewer spaces. Fields deemed unused, meaning they hold no value on any work item, sit on no screen, are not required, and appear in no workflow or form, lose their association.
Why it matters
The dev.to author points to the quiet failure mode for mid-sized sites: scripts that only read the old API will not crash. They will keep returning stale numbers and feeding them into reports nobody has audited in a year. Write-side automation fails loudly with 404s, which is at least easy to catch. Admins should audit integrations against the new endpoints, sweep up orphaned schemes, expect a longer scheme list than before, and treat 'new field isn't showing' reports as a scheme membership problem first. Old bookmarks for the field configuration admin screens now redirect to the Field schemes page, found under Settings, then Work items.
- #jira
- #atlassian
- #project-management
- #rest-api
- #cloud