[MGNLUI-7056] Move action does not contain DropConstraint configuration Created: 08/Mar/22  Updated: 20/Jul/22  Resolved: 07/Apr/22

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.17
Fix Version/s: 6.2.18

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 0
Labels: nucleus
Remaining Estimate: Not Specified
Time Spent: 1.75d
Original Estimate: Not Specified

Issue Links:
Problem/Incident
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:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Nucleus Quality Maintenance
Sprint: Nucleus 7
Story Points: 3
Team: Nucleus

 Description   

Steps to reproduce

  1. Create a constraint on a content app to restrict which nodes can be moved inside e.g, at Assets app switch the mgnl:asset primaryNodeType to mgnl:folder
  2. Go to the app (Asset) and drag and item within other which should not be allowed (an asset within other asset)
  3. Check Drag and Drop allows it
  4. Now click on another item (asset) and clic on Move action on the action bar (or right click -> Move)
  5. Check that moving an asset inside another one is not allowed

Expected results

Drag and Drop movement and Move action behaves the same

Actual results

Drag and Drop movement and Move action do not apply the same rules when moving items

Workaround

N/A

Development notes

This is just an example with the Assets app. In the linked ticket, there is a full example and the definition needed to reproduce it in a custom content app



 Comments   
Comment by Ashraf Khamis [ 07/Apr/22 ]

Doc update: https://git.magnolia-cms.com/projects/DOCUMENTATION/repos/product-docs/pull-requests/990/overview

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