[PAGES-378] Reinstate "Duplicate component" action Created: 07/Jan/21 Updated: 03/Dec/21 Resolved: 30/Aug/21 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | 6.2.10 |
| Fix Version/s: | 6.2.11 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Julie Legendre | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | VN-Testing, maintenance, ui-team-support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Epic Link: | UI framework implementation | ||||||||||||||||||||
| Sprint: | UI FW 35 | ||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||
| Description |
|
The Duplicate component action is no longer available by default. Consider reinstating it. |
| Comments |
| Comment by Julie Legendre [ 07/Jan/21 ] |
|
Hi luke.trueman, The action has indeed been removed. I've created this ticket to request it be reinstated so I will not update the documentation to remove it from there for now. In the meantime, the customer can use the Copy item and Paste item actions instead (just make sure an area, and not the component, is selected when you want to paste - thanks rkovarik!). Hope this helps. Julie |
| Comment by Julie Legendre [ 07/Jan/21 ] |
|
PO/team, if the decision is made not to reinstate, please let me know and I'll update the docs. Thanks!
|
| Comment by Annick Boehler [ 03/Feb/21 ] |
|
Hello, Thanks |
| Comment by Marvin Kerkhoff [ 23/Jun/21 ] |
|
Is there any update when this will come back into the product? Our customers are asking for it. |
| Comment by Simon Lutz [ 24/Jun/21 ] |
|
marvink2 We aim to add it back in 6.2.11 or 6.2.12. |
| Comment by Marvin Kerkhoff [ 01/Aug/21 ] |
|
Hi Simon, will this be planned for 6.2.12? |
| Comment by Simon Lutz [ 06/Aug/21 ] |
|
Hi marvink2, yes, we will add it as part of 6.2.12. |
| Comment by Anne Meister [ 27/Sep/21 ] |
|
Hi Simon – I just looked through the release notes of 6.2.12 and can't find this issue in there. Is it part of the release or will it come later? |
| Comment by Simon Lutz [ 27/Sep/21 ] |
|
Hi Anne, yes, it is solved in 6.2.12 - you'll find the ticket on the changelog and can see the result on our demo which is running on 6.2.12 now. We don't add all the single bug fixes to the release notes, sorry for that. Best regards, Simon |