[MAGNOLIA-6702] Add switch for restoring including descendants and read rule from command context Created: 21/Jun/16  Updated: 09/Feb/17  Resolved: 04/Jul/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.15, 5.4.8, 5.5

Type: Improvement Priority: Neutral
Reporter: Robert Šiška Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 4.75h
Original Estimate: Not Specified

Attachments: PNG File 5315-restore-message.png    
Issue Links:
Relates
relates to MGNLDAM-606 Error restoring a deleted asset to it... Closed
relates to MAGNOLIA-6157 Allow to configure RestorePreviousVer... Closed
dependency
is depended upon by MGNLUI-3921 Adjust restore previous version actio... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Date of First Response:
Sprint: Kromeriz 51
Story Points: 2

 Description   

Add possibility to specify the rule for restoring previous version.
Read the rule from command context.



 Comments   
Comment by Mikaël Geljić [ 24/Jun/16 ]

had We should reopen that, based on our conclusions the other day, or do you prefer to work with a follow-up? (would be cheating with story points )

Comment by Jan Haderka [ 24/Jun/16 ]

Honestly I don't mind either way. So reopening as it is easier

Comment by Julie Legendre [ 06/Jul/16 ]

I think a message needs to be tweaked in 5.3.15 :

  • In the Assets app, delete a folder with sub items.
  • Select the folder and click Restore previous version (not Restore incl. subnodes)
  • (Erroneous) Message appears saying: Previous version of one item and its descendants has been restored.
  • Only the parent folder is restored.

It should really say something like: Previous version of one item has been restored.

Generated at Mon Feb 12 04:17:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.