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!

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.

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

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.

Hi 0ce3de02489d,

Thanks for the the constructive criticism.

The Blog system in Confluence is something of a tacked on design, with tendrils deep into the core of the product. Whilst templates, drafts, pages and all the related content basically use the same system, Blogs are carved out in their own special systems. With this were some dubious design choices made when Confluence has 5 people working on it that have made it incredibly difficult to fix what is, on the surface, a seemingly trivial problem.

We have made progress on the issue and a lot of it has occurred in the background, but as we've progressed the issue, we've discovered additional edge cases and problems that have required more reworking to correct. There's really no good solution to the problem short of a rewrite, and that's not feasible for the issue we're correcting here.

We will hopefully have a finalised solution soon.

Thanks,
James Ponting
Engineering Manager - Confluence Data Center

How long does it take to fix this? Is there any capable developer available? unbelievable.

When will the bug be fixed? The incorrect time information causes a lot of confusion among users.

Hi 337dfcc64420,

There is not yet an update.

Thanks,
James Ponting
Engineering Manager - Confluence Data Center

Hi there, 

is there any update?

Hi there, 

Is there any update?

Hi there,

Is there any update?

We are impacted by this too - how far off is a solution? 

push

please Atlassian have a look again on this issue.... 
its annoying especially for big customer using LTS version... 

I experience Blog post  problem when Confluence Server is hosted in Central Time zone and user is in Eastern Time zone. 

We're using Confluence 7.13.3 and experiencing this issue.

The wrong timestamp is super irritating and frustrating. We need a fix asap.

We are using a kind of a workaround.

Try it if your blog post macro shows the titles (Content Type to Display dropdown) and if your blog posts usually are not edited after creation.

1. Choose the Recently Updated Macro
2. Set Include these Content Types Only field to blog
3. Check the Hide title checkbox

Additionally, you may also mock the "Blog Posts" header of the blog post macro easily.

BTW @Atlassian: This bug occurs in our second LTS version now (7.13.2) ... It's annoying and it's time to fix it.

In our case the problem was that we switched to docker and didn't changed the timezone. 

https://confluence.atlassian.com/kb/how-to-set-the-timezone-for-docker-container-976780914.html#:~:text=The%20timezone%20value%20in%20Atlassian,e%20TZ%3D.

After chaning the timezone the post creation date is now correct! 

Noticed Ruvi's invite above but must ask: Why is this session needed? Isn't the bug obvious if the creation timestamp does not contain the time?

Community post: https://community.atlassian.com/t5/Confluence-discussions/Looking-for-research-participants-for-Confluence-blogs/m-p/1812067#M8970

Do you know when there will be an update to fix this?

Hi everyone,

A quick update and a request for help.

We've been investigating the best options. However, due to the complexity of the issue we need your help to validate the direction to take.

We are planning to run a few concept testing sessions over the next couple of weeks and would love if you could participate and give us your feedback. 

What's involved?

• Sessions will be approximately 45 minutes in length and conducted remotely over video conference, with our team in Sydney.

How do I participate?

• If you're interested in speaking to us, please send us an email at rpit@atlassian.com

• We will confirm a few details before sending through a calendar invitation with video conference details

• During the session, we will ask you a couple of questions around the problems you're facing and show you a couple of concepts we are exploring to better understand if it solves the issue.

• As a token of our appreciation, you'll receive a thank you gift following the completion of your session.

We can't guarantee that we will be able to speak with everyone but we definitely appreciate your interest and enthusiasm to help us make Confluence easier and more enjoyable to use.

Thanks,

Ruvi | Product Designer, Confluence Server and Data Center

what is the status here? it can't be that this issue has been around for 10 years and nothing has happened.
the atlassian service is the worst that there isn't even a name for it. just ridiculous.

Also the "affects versions" list is incomplete - as it also affects the Enterprise (LTS) version 7.4.6 too. You would have thought that might help it get fixed?

The ticket has the highest priority and nothing has been done for more then a month.

Just echoing what others have said, our users who need to publish on specific dates for client-facing updates run into this issue frequently. This has led to confusion especially with our users who are in different time zones. Thanks Atlassian for getting this in the sprints starting in so we can get closer to a resolution.

Even using the workaround with sorting by "modified" our processes/usage requires sorting by "creation". We would highly appreciate having a fix for this issue. Many Thanks

Another 7.4.8 installation is affected 

Dear Atlassian.

We receive more and more tickets from end-users because in some teams blog post dates are critical (some processes depends on posting date). So for some users this small defect is extremely severe.

Confluence DC 7.4.8.

Best regards,
Nikita Dvorkin
on behalf of SAP SE

We also using 7.4.4 LTS release, facing same issue. Please fix this.

We are also on 7.4.6 LTS release - and have these weird "out-by-a-day" dates appearing for blog posts. Please fix.

Hi

Confluence 7.11 is also affected.

Best,
Marcus

Hi

I am also facing the issue in 7.4.6, which is the current LTS version. Please fix.

Thank you and best regards,
Roman

Hi,

Same problem in Confluence 7.4.6 LTS. Thanks to correct it.

Best regards,

Hi macom,

The latest Refined release just addresses some visibility issues regarding colors and contrast for the date/timestamps on the news modules - But I can see how the wording might be confused with this issue/ticket. We're still relying on Atlassian's API for getting the blog post data & information so it will continue to display wrongly with or without Refined in that regard until this ticket is addressed from the Confluence side. If you have any questions or issues with Refined for Confluence you're welcome to reach our on our support portal and we'll help you out. Hope that clears it up a little!

Best regards,

Dennis 

there is a new update 7.0.1 from Refined. After I installed it, it still does not work. According to the fixreport the posts on the news page are resized and sorted but the timestamp is wrong again.

Bug-fixes
Fixed an issue where upgrading with legacy or corrupt advanced theme still present would cause the app to crash and not work properly
Fixed an issue where the Refined Sites would not render properly while using Internet Explorer 11.
Improved the visibility of dates in the News module listings when using Image feed.
Fixed an issue where links weren't clickable in the Spaces module.
Addressed a compatibility issue where K15t's Scroll Version didn't work with the Refined page tree macro
Fixes print styles to only include page content when printing
Improved the global menu render for small screens by rending the icons smaller.

Is there already something new here, because this function is really important. Thanks

Hi there

Thanks for your additional information and sharing what you have been seeing. I wanted to confirm that we're actively working on this one and investigating the best options. We understand that the day/time of the author(s)/audience is relative and that this can be confusing when published, particularly when they all have a 00:00:00/midnight timestamp. I'll get the team to share the direction we are taking once we've completed testing.

Thanks
Makisa | Senior Product Manager, Confluence Server and Data Center

We have a similar issue in our Confluence 7.3.4 / PostgreSQL

• Server/JDK TZ: UTC
• User TZ posting the blog: Athens/Greece

Just posted a blog, selected today 25/Sep as posting date, however the creation date was set to "2020-09-24 21:00:00"

"contenttype";"title";"creationdate";"lastmoddate"
"BLOGPOST";"Testing blogpost dates";"2020-09-24 21:00:00";"2020-09-25 07:34:39.658"

Really strange behaviour.

Here is the database row for a post I created just now...

[local] postgres@confluence=# select * from content order by contentid desc limit 1;
┌─[ RECORD 1 ]─────┬──────────────────────────────────┐
│ contentid        │ 64127064                         │
│ hibernateversion │ 2                                │
│ contenttype      │ BLOGPOST                         │
│ title            │ daily log                        │
│ lowertitle       │ daily log                        │
│ version          │ 1                                │
│ creator          │ ff80808157669a4c01576be292060003 │
│ creationdate     │ 2020-09-25 00:00:00              │
│ lastmodifier     │ ff80808157669a4c01576be292060003 │
│ lastmoddate      │ 2020-09-25 07:55:11.298          │
│ versioncomment   │                                  │
│ prevver          │ ¤                                │
│ content_status   │ current                          │
│ pageid           │ ¤                                │
│ spaceid          │ 21561345                         │
│ child_position   │ ¤                                │
│ parentid         │ ¤                                │
│ messageid        │ ¤                                │
│ pluginkey        │ ¤                                │
│ pluginver        │ ¤                                │
│ parentccid       │ ¤                                │
│ draftpageid      │ ¤                                │
│ draftspacekey    │ ¤                                │
│ drafttype        │ ¤                                │
│ draftpageversion │ ¤                                │
│ parentcommentid  │ ¤                                │
│ username         │ ¤                                │
└──────────────────┴──────────────────────────────────┘ 

is there already an update? It still doesn't work and this function is probably not only very important for us. We use it every day but it doesn't help us if the sorting is completely shifted. Ask for a solution so that the ticket finally helps many people. Thanks

Thanks Hellas Direct.

There are two entries in the content table in the database for each blogpost. "current" and "draft".

But your solution works only for the creationdate in the draft. Can you confirm that?

Also using Confluence 7.4.3.

Using Confluence 7.4.3 on-prem, we had the same problem.

Our server had UTC timezone which was different from the one used by our users.

Added -Duser.timezone=Europe/Athens in CATALINA_OPTS of setenv.sh and restarted confluence.

Now blog posts appear on the correct date (our users are in Athens).

We urgently need a solution and no reference to a 9 year old ticket from 85 affected User and Company

Confluence 7.4.1 is affected.............

The problem occurs also with us, is there already a solution? The date is displayed retroactively to e.g. "created 14 hours ago

Confluence 7.4.1 is affected.............

Thanks for your recent comments. You may have seen activity on this ticket as we have moved it into our Short Term Backlog and now into our current sprint. We are investigating this issue; I suspect it has been open for a long time based on its complexity. Our team is looking into it and we aim to provide a definitive answer on this one shortly.

Regards,
Niraj Bhawnani
Engineering Manager, Confluence Server
Atlassian

Could you explain "Ranked lower" ?

The bug is now 9 years old!! Unbelievable

HI! as an Enterprise Customer we have created an Issue on Premier Support Level as well - the Business Impact is quite severe now, since we were not aware of this issue beforehand and have relaunched multiple Intranets on regional and corporate level on confluence (distributing corporate informations across all pages and intranets using RSS Feeds)

To make a long story short : we assume there is a warranty for certain functions of the software , and we do need to get a timeline for having this bug fixed - since it has to be reported to C - Level.

https://getsupport.atlassian.com/servicedesk/customer/portal/30/PS-61492

We were expecting this to be fixed in the Confluence Enterprise release 7.4.

However, there is no update now while the version has already been released now.
The Kanban board at https://jira.atlassian.com/secure/RapidBoard.jspa also doesn't show any progress.
Can you please inform us on the planned progress, the bug is really annoying and embarrassing

Hi all,

This bug has been moved from the Long term backlog to the Short term backlog of our development team.

• Atlassian Server Bug Fix Policy

We have also recently created new dashboard that will make it easier for you to see what bug fixes we are working on that will provide you with a view into our short term backlog and includes the following key information:

• Bugs that have been prioritised and are currently being worked on
• Issues or feature suggestions that have been prioritised for development through a project/theme of work
• Version the fix will be shipped in so you can track when the update will be available.

We hope with this dashboard, you can better manage your instance and plan upgrades.

• Confluence Server & Data Center Bug Fix Board

Cheers,
Sattesh Maran

It's really embarrassing that after 9 years the bug has not been fixed yet. This is typical Atlassian!!! The development of Confluence is going at a snail's pace. I am really frustrated. Do something for all the money you get!!!

Thanks all for your recent comments confirming that this is still an issue. I can understand that this is frustrating to see and I'll review this with the team.