[MAGNOLIA-218] Ability to move components between areas Created: 25/Nov/04 Updated: 18/Jul/16 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | samples |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Hugo Lumsdon | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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)
|
||||
| Date of First Response: | |||||
| Description |
|
Currently it seems that component can only be moved within the area on the page in which they were originally created. Really it should be possible to move the components to any area - provided that the area supports the specific type of component. |
| Comments |
| Comment by Boris Kraft [ 25/Nov/04 ] |
|
Thats an old favorite for me |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |