-
Bug
-
Resolution: Fixed
-
Highest
-
2.8, 5.5-beta1, 5.7.1, 5.9.5, 7.0.2, 7.0.4, 7.1.0, 7.3.1, 7.3.3, 7.3.4, 7.4.1, 7.4.3, 7.4.5, 7.6.0
-
43
-
Severity 2 - Major
-
115
-
When testing Activity Streams, new blog posts were showing up with timestamps that were way off. I found that when Streams is querying content from Confluence, every com.atlassian.confluence.pages.BlogPost object has a creationDate property with no time (i.e. the date is correct but the time is 00:00:00). The lastModificationDate property has the correct time, so we can probably work around this in Streams by just using lastModificationDate instead of creationDate for new blog posts.
This might be related to CONF-17872 - that issue was resolved as "not a bug" on the theory that it had to do with different server time vs. user time, but that can't be true in this case because I'm running locally. Also might be related to CONF-21910.
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Gathering Impact
-
-
-
- Long Term Backlog
-
-
-
- Short Term Backlog
-
-
CONFSERVER-23820 On blog posts the created date should be shown
- Closed
- relates to
-
-
- Gathering Impact
-
-
-
- Short Term Backlog
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-22560] Blog post creation date is used as a publish date: it is different to the actual creation time and sometimes stored as midnight
| Remote Link | Original: This issue links to "Page (Extranet)" [ 526065 ] |
A fix for this issue is available in Confluence Server and Data Center 8.5.0.
Upgrade now or check out the Release Notes to see what other issues are resolved.
| Link | New: This issue has a derivative of CONFSRVDEV-26801 [ CONFSRVDEV-26801 ] |
Hi All,
Just a note on the fix for this one.
Firstly, apologies the ticket was updated late, the work was tracked on an internal ticket and not correctly moved to the public ticket.
Secondly, the fix has a limitation of minute level accuracy due to using minutes as the smallest measure of time in our interface time picker. I don't expect this to cause issues, but just in case 
Thanks,
James Ponting
Engineering Manager - Confluence Data Center
| QA Demo Status | New: Done [ 14331 ] | |
| QA Kickoff Status | New: Done [ 14235 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
A fix for this issue is available in Confluence Server and Data Center 7.19.11 and Confluence Server and Data Center 8.4.1.
Upgrade now or check out the Release Notes to see what other issues are resolved.
| Fix Version/s | New: 7.19.11 [ 104748 ] | |
| Fix Version/s | New: 8.4.1 [ 105710 ] | |
| Fix Version/s | New: 8.5.0 [ 104201 ] |
| Flagged | Original: Impediment [ 10510 ] |
| Flagged | New: Impediment [ 10510 ] |
Hi everyone,
I'm still experiencing the issue where the creation date of a blog post (12:10) does not match the displayed date in the macro (13:10), even though I'm using version 8.5.6. According to Atlassian, this should have been fixed since 8.5.0.
Has anyone encountered similar issues or have any solutions?
Thanks!