Fix: QuickEdit: consolidate how "Status > Scheduled" works #76129
Fix: QuickEdit: consolidate how "Status > Scheduled" works #76129oandregal merged 4 commits intoWordPress:trunkfrom
Conversation
…us change to scheduled
github-actions
bot
added
[Package] Editor
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
There was a problem hiding this comment.
Pull request overview
This PR addresses Gutenberg issue #76103 by making the Quick Edit experience consistent with the editor inspector: when a post’s status is changed to Scheduled (future) in Quick Edit, a date/time control becomes available so users can immediately set the scheduled publish date.
Changes:
- Added a new
scheduledDateFieldto the@wordpress/fieldspackage, visible only whenstatus === 'future'. - Implemented a custom edit control using the block-editor’s
PrivatePublishDateTimePicker. - Wired the new field into the editor dataviews schema and the Edit Site Quick Edit modal layout.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/fields/src/fields/index.ts | Exports the new scheduledDateField from @wordpress/fields. |
| packages/fields/src/fields/date/scheduled/index.tsx | Defines the new field (scheduled_date) with visibility tied to scheduled status. |
| packages/fields/src/fields/date/scheduled/edit.tsx | Adds the date/time picker edit UI for scheduled posts. |
| packages/fields/README.md | Updates autogenerated API docs to include scheduledDateField. |
| packages/editor/src/dataviews/store/private-actions.ts | Registers scheduledDateField in the post-type schema fields list. |
| packages/edit-site/src/components/post-list/quick-edit-modal.js | Adds scheduled_date into the Quick Edit form under Status. |
Comments suppressed due to low confidence (1)
packages/fields/src/fields/date/scheduled/index.tsx:25
- The doc comment reads "ScheduledDate Field." which is inconsistent with the other field docs in this package (they typically use sentence case and mention the entity type, e.g. "Date field for BasePost."). Updating this comment will also improve the autogenerated API docs in
packages/fields/README.md.
/**
* ScheduledDate Field.
*/
export default scheduledDateField;
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| type: 'datetime', | ||
| label: __( 'Scheduled Date' ), | ||
| getValue: ( { item } ) => item.date, | ||
| Edit: ScheduledDateEdit, |
There was a problem hiding this comment.
It'd be best that the existing date field and this one use the same Edit component. Meaning that we don't need this custom Edit, we can just reuse the bundled one.
There was a problem hiding this comment.
Hi @oandregal, Thanks for the suggestion. I initially tend to use the same one, datetime on the new scheduled_date field, but the thing is it does not match with the exact post editor screen that we are intend to.
If we need to match the funcationality then datetime will work, but if need to match exact same consistency to post editor screen, customEdit would be the thing to go.
For now, not updating the PR with bundled theme, will wait for the way to go.
See the below screenshots,
| With bundled datetime | With custom Edit | Post Editor screen |
|---|---|---|
 |
 |
 |
There was a problem hiding this comment.
It's best to start with the bundle one, and iterate from there.
Then, in a follow-up PR, we may offer a compact variant of the datetime that only displays the datetime-local input, not the calendar via configuration. Essentially, we'd support something along these lines:
Edit: {
isCompact: true
}and the result would be that only the datetime-local component is displayed.
There was a problem hiding this comment.
That makes sense @oandregal, Thanks for the review. I will update the PR shortly with the change and use the bundled one instead of custom edit for now.
There was a problem hiding this comment.
Hi @oandregal, The above is now updated. Used the bundled datetime component for both date and scheduled date field.
There was a problem hiding this comment.
I do have created a followup issue to track the same - #76234
What?
Closes #76103
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast
Screen.Recording.2026-03-06.at.2.54.16.PM.mov