[wp-trac] [WordPress Trac] #32386: Draft's Last Modified date incorrect if it is Scheduled

[WordPress Trac]

#32386: Draft's Last Modified date incorrect if it is Scheduled
--------------------------+---------------------------------
 Reporter:  lastnode      |       Owner:  obenland
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  4.3
Component:  Date/Time     |     Version:  4.2.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, administration
--------------------------+---------------------------------

Comment (by helen):

 I hate potentially rabbitholing tickets by asking us to pull back, but I
 think this warrants it. There is clearly a bug here, in that this is a
 subpar and rather inaccurate column of data. What data '''should''' this
 column contain and in what situation?

 If we operate off the premise that data displayed in the list table is to
 help users make decisions about what to do next (is this the draft I'm
 looking for, do I need to delete this thing that is past its prime), I
 don't think the date column is doing a great job. I have no idea what
 happens when you go to publish a draft post with a date you've set in the
 past. I'd even love to know when a published/scheduled post was last
 modified. And why does a private post show last modified even though it
 appears on the front-end with its original post date? Is potentially two
 dates too much to have in that column?

 We can fix the draft modified date itself on its own, as the date sort
 thing is really already a problem once we're in this situation. I just
 don't think it's our only problem here.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32386#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform