Currently, order revisions are not also versioning entities referenced by fields on the order (i.e. line items) so data is lost between saves. We need to figure out how to do this cascading save properly so that a new line item revision is created when a line item is modified (i.e. quantity or price altered) and the changes correspond with an appropriate order revision somehow...

Comments

rszrama’s picture

rszrama commented
Assigned: Unassigned » damien tournoud
Issue tags: -dcsprint3 +dcsprint6, +rcblocker

I'm not sure if my original description of this issue is correct. However, since Damien is currently unifying our entity controllers, I'm going to push this to him for review. As an rcblocker, we need to either resolve this or determine it's not a blocking issue.

See: #1181534: Refactor entity handling

deggertsen’s picture

deggertsen commented

What is the status on this issue? It seems that there may be some relation here to the following issues, but I'm not sure. Maybe all of the issues related to order revisions need to be tagged that way?

#1651368: Allow the order state / status update actions to set a log message
#929266: Add revision history to transaction view pages
#804850: Integrate Order Revisions with Views

bojanz’s picture

bojanz commented
Issue summary: View changes
Status: Active » Closed (outdated)