[MGNLFORM-14] Cannot move field from one field set to another Created: 15/Jan/09  Updated: 18/Jul/16  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Form Module
Component/s: field
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Boris Kraft Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
dependency
is depended upon by MGNLUI-1786 Cannot move page component to another... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Although the GUI allows me to drag a field from one field set to the new bar below a second field set (and correctly states "Move the paragraph selected above this one" - which by the way should say "Move the selected paragraph above this one") it doesn't work. The form field is not moved.

I think it would be very useful if form fields can be moved between field sets, but at the very minimum it should not indicate it works and then fail.



 Comments   
Comment by Philipp Bracher [ 16/Jan/09 ]

This is not trivial. As each field set is a different container and moves between containers don't work.

As an interim solution we could drop the fieldset and just have a separator element.

Comment by Magnolia International [ 16/Jan/09 ]

As a happier note, i fixed the message in MAGNOLIA-2556

Comment by Zdenek Skodik [ 18/Jun/10 ]

I guess this would be a matter of new 5.0 AdminCentral.

Comment by Christopher Zimmermann [ 05/Dec/13 ]

Issue actually must be solved in UI project, see linked ticket. Base requirement is moving page components between areas. The fieldsets are areas.

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.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:36:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.