Jira Field Scheme Migration: What Admins Should Check
ملخص
Pixel shares findings from Jira Cloud's automatic shift from field configuration schemes to field schemes. A test site showed 43 schemes for 59 company-managed spaces, including 24 unlinked schemes; the legacy API still returned HTTP 200 for reads but returned 404 for writes, a key concern for outdated scripts and reports.
DEV Community
Jira field schemes replaced field configuration schemes
On 20 October 2026, Carol Low from Atlassian answered a question under the Community's field schemes FAQ, a post that had 56,420 views when I checked on 15 November. Sites on continuous release tracks already had field schemes, she wrote, and sites on bundled tracks were scheduled to get them on 10 November. (A release track is the setting that decides when Atlassian's changes reach your site.) So if you run Jira Cloud, your field configurations and field configuration schemes have most likely been converted by now, automatically, in your site's maintenance window. We looked at what that conversion left behind on our own test site on 15 November. The new Field schemes page listed 43 field schemes for 59 company-managed spaces, and 24 of them weren't linked to any space. Meanwhile the old field configuration API still answered with HTTP 200, with numbers that no longer match the new model: 740 items in our default configuration against 471 fields in the default field scheme. Writes through the old API came back 404. If you look after a Jira site with somewhere between 50 and 2,000 people on it, the part to worry about is the scripts and reports nobody has touched in a year. Scripts that only read won't fail. They'll read stale numbers and carry on. A space is Jira's current name for a project, and the REST API still says project. A work type is what older screens called an issue type. Our test site is wolfaenpak.atlassian.net, which is on a Jira plan with a sandbox (Premium or Enterprise) and which we keep for exactly this kind of thing, and the numbers below come from that site after the real migration. What we found on 15 November 2026 We had 43 field schemes after the migration. 19 were linked to spaces, one of them only to a space in the trash. The other 24 were linked to none (I'll call those orphans), and all 24 were schemes for service spaces, meaning Jira Service Management spaces, that no longer exist. 42 of our 59 live company-managed spaces share the Default Field Scheme. The other 17 each have a scheme of their own, and 12 of those were made by our own test-data script through the new API. The old read endpoints still answer with HTTP 200, but the numbers don't match the new model: 740 items against 471 fields for the default, 165 against 157 for a service space, 170 against 180 for a test space. Asking the old API "which scheme does this space use" gave back an empty list for all 70 spaces, company-managed and team-managed. An old write returned 404 "The field configuration was not found." on an id that the old read still answers for. Through the new API, the same change worked once we left one setting out of Atlassian's example. Jira refused to delete the default scheme and a scheme in use, and it deleted an orphaned scheme in one call. What Jira field schemes replaced: field configurations and field configuration schemes Until this year, a Jira admin needed two objects to decide which fields a space shows. A field configuration listed the fields and marked each one hidden, optional or required. A field configuration scheme then mapped work types in a space to field configurations, so a Bug could use one configuration and a Story another. A field scheme replaces both. Atlassian's What are field schemes? page puts it like this: "Field schemes allow you to control which fields appear on your work items and how those fields behave across different spaces." Each space uses exactly one field scheme, and one scheme can serve many spaces, says the page on associating a space with a field scheme. If a field isn't in a space's scheme, it doesn't show up in that space. Two older pieces keep their jobs, and it helps to keep them apart in your head. Field contexts now only set the content of a field, meaning default values and the options in a dropdown, and they no longer hide a field from a space. Atlassian's general availability post says each field now gets a global context that can't be deleted. Screens, screen scheme...

Powered by Readybot.io