Skip to content

Fix Jira create issue handling for empty create screens - #1895

Open
BakedSoups wants to merge 2 commits into
atlassian:mainfrom
BakedSoups:fix/jira-empty-create-screens
Open

Fix Jira create issue handling for empty create screens#1895
BakedSoups wants to merge 2 commits into
atlassian:mainfrom
BakedSoups:fix/jira-empty-create-screens

Conversation

@BakedSoups

@BakedSoups BakedSoups commented Jul 3, 2026

Copy link
Copy Markdown

Fixes #1852

Summary

  • Detect Jira create metadata with no fields beyond project/issue type.
  • Show an explanatory warning instead of an empty form in both create issue surfaces.
  • Prevent create submission when the selected work type has no configured create fields.
  • Surface Jira field-level API errors in the error banner instead of an opaque 400 response.
  • Add agent notes for the create issue surfaces and local dependency install gotchas.

Testing

  • Added React/reducer coverage for empty create screens and Jira field errors.
  • Ran git diff --check.
  • Could not run Jest/lint locally because dependency install requires private Atlassian packages: npm ci reports lockfile drift, and npm install --package-lock=false fails on @atlassian/assets-workspace-host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create dialog renders empty form + generic 400 on submit when project Field Configuration ships an empty create screen (Jira DC)

1 participant