[LIVECOPY-317] Maintain push functionality when moving a Livecopy out of ROOT Created: 21/Jun/22  Updated: 17/Aug/22  Resolved: 09/Aug/22

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 3.2.8
Fix Version/s: 3.2.9

Type: Improvement Priority: Blocker
Reporter: Roberto Gaona Assignee: Jesus Alonso
Resolution: Fixed Votes: 2
Labels: cs-bk
Σ Remaining Estimate: 0d Remaining Estimate: 0d
Σ Time Spent: 6.75h Time Spent: 6.75h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File image-2022-07-19-09-45-21-010.png    
Issue Links:
causality
supersession
supersedes LIVECOPY-315 New master content is not pushed to m... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
LIVECOPY-332 QA Sub-task Completed Thuy To  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: AuthorX Support
Sprint: AuthX 15
Story Points: 5

 Description   

When creating multiple LCs, if the client wants to organize them into a page node / site, the push functionality won't work for new components added to any pushed page, while it will work for edited and removed components.

Here are the steps followed to reproduce the issue:

  1. In the pages-app: Create the node structure /MASTER/HOME/About, where "About" is a simple page template with header and content
  2. Create the root note /tenants
  3. Make two live copies from the node /MASTER/HOME, renamed them tho HOME_FR and HOME_US
  4. Move the live copies from / (root) inside the /tenants/ node.
  5. Alter something in /MASTER/HOME/About, e.g. added a header element
  6. Select /MASTER/HOME and use the Action "PUSH master changes incl. subnodes"; alternatively we tried selecting /MASTER/HOME/About and used the action "PUSH master changes"


 Comments   
Comment by Jürgen Brömmer [ 15/Jul/22 ]

Hi rgaona rgange 

imho if pushing to copy one works but it does not push to copy two (and three and four and ...), this is clearly a malfunction (i.e. bug), even if this never worked before. 

If the nodes have been moved or not should not make a difference here.

What do you think?

Generated at Mon Feb 12 02:27:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.