[MGNLUI-5407] Harden various editor implementations/incarnations Created: 08/Oct/19  Updated: 29/Nov/19  Resolved: 29/Nov/19

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: 0.5h Remaining Estimate: Not Specified
Σ Time Spent: 3d 47m Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-5416 Optimize non-light dialog UI Closed
depends upon MGNLUI-5417 Type aliases for Action/Availability ... Closed
depends upon MGNLUI-5511 Harmonize dialogs - follow up Closed
depends upon MGNLUI-5426 Harmonize light and strong dialogs Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-5419 Replace search box with filters in ch... Sub-task Closed Federico Grilli  
MGNLUI-5438 Implement move dialog UI Sub-task Closed Roman Kovařík  
MGNLUI-5439 Let multiple editor sub-apps be open ... Sub-task Closed Adam Siska  
MGNLUI-5440 Keep the detail sub-app tab caption i... Sub-task Closed Šimon Demočko  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: UI framework: forms, dialogs, content editing
Sprint: UI Framework 8, UI framework 9, UI Framework 10, UI Framework 11
Story Points: 13

 Description   

A list of things that would be nice to do (!! extract the sub-tasks/separate tickets):
– what to do with the search box? In m5 realm it was implemented as a so-called content tool and in case of JCR it would fire up a full-text search. Can we use column filters (better)? Or maybe a composition of workbench and search box UI?

  • add more type aliases where approrpriate (actions/action availability rules/...)

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