[MGNLUI-2101] Can't move properties in Configuration app Created: 16/Sep/13  Updated: 08/May/14  Resolved: 06/May/14

Status: Closed
Project: Magnolia UI
Component/s: configuration, user interaction
Affects Version/s: None
Fix Version/s: 5.3

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Build #3428 (16.09.2013 09:23:56)


Attachments: PNG File Bildschirmfoto 2013-09-16 um 11.15.27.png    
Issue Links:
Cloners
is cloned by MGNLUI-2877 Can't move properties via action in C... Closed
dependency
depends upon MAGNOLIA-5764 Utility method to move properties 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   

While I can move content nodes and folder, I can't move properties.

According to research by Sasha, this seems to be technically feasible, but requires some significant changes in the move node action.



 Comments   
Comment by Jan Haderka [ 05/May/14 ]

see
https://git.magnolia-cms.com/gitweb/?p=magnolia_ui.git;a=shortlog;h=refs/heads/move-fix-review
and
https://git.magnolia-cms.com/gitweb/?p=magnolia_main.git;a=shortlog;h=refs/heads/move-properties

Comment by Daniel Lipp [ 06/May/14 ]

New type NodesAndPropsDropConstraint should get proper unit-tests (at least for #allowedAsChild).

Also it seems like this ticket requires a new NodeUtil method that's not yet pushed.

Comment by Jan Haderka [ 06/May/14 ]

added unit test on the branch

Generated at Mon Feb 12 08:53:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.