Fields missing from Create Issue modal — all projects on one Issue Type Screen Scheme — no config ch

Question

Hi Atlassian Community,

As of this morning (July 30, 2026) the Create Issue modal for all 14 projects using our "Dev: Issue Type Screen Scheme" is missing multiple fields that were working yesterday. No configuration changes were made overnight.

Missing fields:
Reporter, Labels, Team (customfield_10001), Attachment, Start date, Due date, Fix versions

What we've ruled out:

* ✅ Fields ARE on the screen ("Dev: Task create" — verified in Settings → Screens)

* ✅ No screen or scheme changes since June 16 (audit log verified)

* ✅ Fields are NOT hidden in the field configuration

* ✅ Field contexts are correct

* ✅ No Atlassian platform incidents today

* ✅ getCreateIssueMetadata API confirms only 13 fields returned vs 16+ expected

Key finding:
A different project (SAEPDLTDEV) on its own separate Issue Type Screen Scheme renders all fields correctly — including the exact same fields that are missing in the affected projects. Same field config, same screen fields, different scheme = different runtime result. This points to a backend caching or scheme resolution issue specific to our "Dev: Issue Type Screen Scheme."

Attempted workaround:
Made a trivial change to the "Dev: Task create" screen (moved a field, saved, moved back) to force a cache bust — did not resolve the issue.

Impact: 14 projects, 50+ users blocked from creating fully-populated issues.

Has anyone seen this before? Is there a way to force Jira Cloud to re-resolve a scheme's field list? Tagging @atlassian for visibility.

Trudy P Claspill · Answer

I missed the detail about the fields being missing from the metadata. Good catch @Gabriela - LeanZero

Gabriela - LeanZero · Answer

Hi @Lindsay Anthony, the Hide unused fields toggle doesn't fit here - that one hides fields per user in the UI. Your getCreateIssueMetadata check shows the fields missing from the API response itself. Different animal entirely.

This lands in the class where forum troubleshooting usually stalls, because the actual context/scheme resolution runs server-side and nobody outside Atlassian can see it. Raise a support ticket and hand them exactly what you posted here - the createmeta output plus the SAEPDLTDEV comparison already isolates it to the scheme's resolution, which saves them a round of the diagnostics you already ran.

Trudy P Claspill · Answer

Hello @Lindsay Anthony

What is the type of the space that is affected? Click the ellipsis button next to the space name in the navigation panel on the left and tell us what the last two lines say. It will be something like:

Software space
Company-managed

Can you provide a screen image of what you are seeing?

Does you modal look something like this?

Or like this, with an ellipsis/More Actions button in the upper right?

The first is a new streamline work item creation experience. Refer to this for more information.

Introducing the new, streamlined Create experience in Jira

From there you can get the more expansive experience in the second image by clicking the Show More button in the upper right corner.

If your modal looks like the second image and you are still not seeing all the fields then ellipsis button to reveal these options.

The Hide unused fields option may be hiding fields, if enabled.

You can check the Configure fields option to see if the affected users has chosen to hide some fields.

You can check the Find your field option to see if it can provide an explanation as to why a specific field may not be appearing.