I noticed since version 7 of Confluence the 'creationdate' field for blogpost 'contenttype' in 'content' db table doesn't get the proper timestamp.
For exemple for today Nov 20th 2019, if the server is UTC and the client side browser is UTC too, every new blog will get the 'creationdate' field filled up like this, for 'current' content_status:
'lastmoddate' field stays accurate though which proper hh:mm:ss recording.
When you get many new blogposts a day, they sort out sort of any order. Which is very annoying when these new blogposts are related to time specific actions from different teams.
Untill version 6.15 these blogposts were ordered by latest creationdate first and that was quite logical.
If there is a trick to fix that issue I'd be very grateful to know it, thanks!
Seems this is a very old bug which is back with Confluence versions 7 (at least both 7.0.4 & 7.1):
(Severity 2 - Major)
so annoying to say the least, especially considering the above ticket was opened on 21/May/2011... and closed ... 09/Sep/2019, with no check for new versions 7 unfortunately...
Blog in Confluence is quite a useless feature with such an issue I reckon...
It’s been great to hear from fellow users over the last few weeks about the best tips and fun moments you’ve had working on Confluence since the transition to working remote. I’d love to keep the c...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events