updated_at not changing on mass update attributes.

[tzyganu]

This is inspired by a question for Magento 1.
I tested on Magento 2-alpha 104 and it behaves the same as in Magento 1.
When mass updating products using the Update attributes from the product admin grid, the updated_at attribute does not change.
It is only changed when explicitly calling $product->save().
This may be a philosophical question "Should updated_at be changed when bulk updating products?".
I would say "Yes". It should be changed independent of the source of the modification.
This is applicable for all EAV entities.
If you have a different view on the issue, please share.

[verklov]

Thanks for this suggestion, @tzyganu! We will consider this when improving the way Magento 2 behaves.

[vpelipenko]

Internal ticket: MAGETWO-31537

[pavlindrom]

We're currently validating an extension for Magento 2 where we have a products api sync and this issue is causing us to miss data. I hope to resurrect the ticket (it's almost a year since it's been "acknowledged", and as of 2.0.2 there is no change.

We are considering adding a observer to the update action, and set the updated_at for all the affected products, but as it will be hacky, we'd rather have it part of the product.

[miguelbalparda]

+1

[erikhansen]

I would agree with @tzyganu that the updated_at field should get updated regardless of the source of the change.

[gtaylor44]

Any updates on this issue? The updated_at column should get updated if you change details about a product, etc. Surely this is an oversight?

[samtay]

+1