[MGNLDMS-253] CLONE -Wrong comment is used when restoring version Created: 29/Nov/12  Updated: 29/Jan/13  Resolved: 04/Dec/12

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.6.5

Type: Bug Priority: Neutral
Reporter: Andreas Weder Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-3409 Wrong comment is used when restoring ... Closed
causality
relation
is related to MGNLADMLEG-18 VersionCommand saves comment property... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When restoring a version, it seems that the comment of a particular version is not restored.

I've created a node and activated it. I then deleted the node, activated the change, but rejected the subsequently created work item. I activate and rejected again. I've then opened the Versions dialog in AdminCentral on the node and restored to a previous version (2nd version from above, dating 11/25/10 4:07pm).
The node was restored properly, but the comment is still the same as in the last version, which is possibly wrong, but certainly confusing.



 Comments   
Comment by Milan Divilek [ 04/Dec/12 ]

Port to 5.0 can't be done right now. Because 5.0 doesn't support metadata. This issue should be ported after refactoring VersionCommand. MGNLUI-330

Comment by Milan Divilek [ 04/Dec/12 ]

Reopened due dependency on MAGNOLIA-3409 where we add into method addComment version number argument.

Generated at Mon Feb 12 00:49:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.