Purchase date on admin screen is always *:07:00

[RocketmanLabs]

1. Go to the admin screen and view the first page of Orders.
2. Note that the date/time under the heading Purchase Date is always *:07:00
3. Time stamp appears correct in REST API return values ('created_at' attribute).

[pboisvert]

Can you provide more info to troubleshoot such as which version you are using? How were the orders created? Was this an upgrade from a previous version? etc...

[RocketmanLabs]

This is a recent upgrade to Magento 2.1. The orders came in from people buying our stuff on the website. Screen cap follows:

[pboisvert]

thanks--that should help narrow down the possible cause.

[Krapulat]

I have the same problem.

[ghost]

Same issue here as well. Using 2.1 CE.

[kennylawrence]

same here
FYI I am using a database that was migrated from 1.9.2.2ce -> 2.1ce

[xaviermarchegay]

The date format specified in the sales grid is wrong : 81de258

Instead of displaying the minutes (mm), the month is displayed (MM).

The right format is MMM dd, YYYY, H:mm:ss A

edit: thanks @LucScu

[xmav]

Hi @RocketmanLabs , thanks for reporting this issue. Internal ticket MAGETWO-53138 was created.

Best,
Maksym

[LucScu]

@xaviermarchegay the correct format is
<item name="dateFormat" xsi:type="string">MMM dd, YYYY, H:mm:ss A</item>

[PascalBrouwers]

I also have this on a clean install of Magento 2.1.2

[LucScu]

@PascalBrouwers You have to look at the xml in question: if you see the old code the issue is still present.

[claridgicus]

Hey guys, this timestamp issue is still featuring in 2.1.2 - is it going to be resolved in 2.1.3 or?

[bh-ref]

the issue is still present in CE 2.1.3

[maximehuran]

I confirm

[vrann]

Fixed in #8336

[bh-ref]

@vrann thank you for fixing it!

[devtinku]

@LucScu Your suggestion works if i change it in core file. How can i do the changes without touching core files.

I tried with below steps but its not worked ::

1. Copied sales_order_grid.xml to custom module
2. Cleared cache

[LucScu]

@devtinku i suggest you to not lose your time on how to make this fix in a custom module. Keep it in the core file and add the file to git so you could see future update changes. Then wait for magento version with official fix, after this you could remove file from repo.

[magento-team]

Internal ticket to track issue progress: MAGETWO-70771

[andidhouse]

Shure @magento-team - this bug is one year old and now you create an internal ticket to track the progress of this? Wow - would you be so kind to think about fixing bugs instead of reporting hundreds of internal tickets without any bugfix?

[steverobbins]

@magento-team Here's your weekly reminder that we're still waiting for this fix.

[kennylawrence]

oh. my. gosh. how do you turn off tracking for bugs? this is embarassing.

…

On Fri, Aug 18, 2017 at 6:13 PM, Steve Robbins ***@***.***> wrote: @magento-team <https://github.com/magento-team> Here's your weekly reminder that we're still waiting for this fix. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5651 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANScYVez3exTkUaILF0hvrmU87JNyf_Gks5sZhqfgaJpZM4JM5fZ> .

[OZZlE]

Still happens in 2.1.7....