[PAGES-306] Support copy / paste components between pages Created: 09/Jun/20  Updated: 09/Jul/21  Resolved: 29/Jul/20

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2.1
Fix Version/s: 6.2.3

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Šimon Demočko
Resolution: Done Votes: 2
Labels: 62-UI-1
Remaining Estimate: Not Specified
Time Spent: 4h 37m
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLUI-6078 CLONE - Support copy / paste componen... Closed
Issue split
split to PAGES-320 Clipboard component cannot be pasted ... Closed
Relates
relates to PAGES-308 Support cut/paste of components betwe... Closed
relates to MGNLCE-248 UI test for copying component in one ... Closed
relates to PAGES-314 Component templates with same name ar... Closed
causality
duplicate
duplicates MGNLUI-6033 Component copy functionality is stron... Closed
relation
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Migrate apps to new UI framework
Sprint: UI FW 7
Story Points: 5

 Description   
  1. Start with 2 pages open in the pages app, page A and page B. Both pages use the same page template.
  2. in page A, select the first component in the main content area of the page
  3. click "Copy item" in the menu
  4. swap to page B
  5. select the main content area of the page
  6. paste item is not available in the menu (visible, but disabled)

--> Improvement: Support copy / paste components between different pages.
Functionality was present in Magnolia 5.7.x

Dev note

We'd like to have delegates and decide which one to delegate to based on context (browser/detail).



 Comments   
Comment by Viet Nguyen [ 23/Jun/20 ]

Comment from mboehm:

When can we expect a fix for this bug to progress through to a release? There doesn't appear to be any suggested timeframe when this maybe resolved.

The Jira PAGES-306 suggests this is an Improvement issue, which we strongly disagree with as this was functionality present in Magnolia 5.7.x. We are finding this issue as a blocker to our upgrade to 6.2

Comment by Šimon Demočko [ 25/Jun/20 ]

I'd say filing a followup is a good idea, worst case it just won't be prioritized. Ticket will increase visibility of the improvement, the valuable comment can get lost in time. Created PAGES-308. Feel free to add details, if I missed something.

Comment by Sang Ngo Huu [ 29/Jul/20 ]

QA is done.

But the current support does not meaning enough:

  • I only can copy/paste a component strictly inside an exactly template (same template).
  • But to me, it should be support more, for Eg: if you copy text-image component, you can paste to area allowed text-image component

sdemocko WDYT?

Comment by Šimon Demočko [ 29/Jul/20 ]

True - we checked and this behaviour was as strict even in M5. Which means the feature was not heavily used by customers, otherwise they would stumble upon this unreasonable restriction. Since the behaviour really is unexpected it's a bug - I filed and linked it under PAGES-320. Thanks for the find.

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