[MGNLUI-4170] Move Before and Move After buttons are disabled when moving node to its direct parent Created: 21/Mar/17  Updated: 28/Apr/17  Resolved: 12/Apr/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4.12, 5.5.3
Fix Version/s: 5.4.13, 5.5.4

Type: Bug Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 0
Labels: move-dialog, usability, ux, working-with-items
Remaining Estimate: 0d
Time Spent: 4.5d
Original Estimate: 2d

Attachments: PNG File screenshot.png    
Issue Links:
causality
is causing MGNLUI-4194 Generalize code for move-availability... Closed
relation
is related to MGNLUI-3900 Show the root node in the "move" dialog 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:
Sprint: Saigon 88, Saigon 89, Saigon 90, Saigon 91, Saigon 92
Story Points: 5

 Description   

Steps to reproduce:

  • Open Asset app, select "/tours/shark_brian_warrick_0824"
  • Choose "Move Asset"
  • In Move Dialog, select "tours"
    => Expected: Move Before and Move After are enabled
    => Actual: Move Before and Move After are disabled (although we can drag and drop that "shark" item before and after "tours" without opening Move Dialog).

~ Site node: This issue occurs in Pages, Asset, JCR and Site app.



 Comments   
Comment by Oanh Thai Hoang [ 13/Apr/17 ]

This ticket has been done QA on branch 5.5. It works well

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