When creating records via "Add New" (quick-create), the backend rejects the mutation if required fields are missing. A proper redesign is needed to have creation forms that defer saving until the record is complete, with clear validation and optional drafts.
# Introduce creation forms for objects with required fields ## Summary When creating records via "Add New" (quick-create) with minimal or no input, the backend rejects the mutation because required fields are missing (`Field "title" of required type "String!" was not provided`). The current approach of auto-filling placeholders (e.g. "Untitled") is a stopgap. We want a proper redesign: **creation forms** that defer saving until the record is complete, with clear validation and optional draft state. ## Problem - Quick-create (e.g. "Add New" on a table) sends a create mutation immediately with whatever input is available - Required fields that aren't provided cause opaque GraphQL errors - Auto-filling placeholders (see closed PR #18616) works technically but creates records with fake data that users must edit afterward — poor UX - Required relations (MANY_TO_ONE) cannot be auto-filled at all; SELECT fields with no options are unfillable ## Proposed solution: creation forms For obje