[MGNLUI-6850] Choose appropriate deprecation strategy for configuration app Created: 27/Aug/21  Updated: 25/Jul/23  Resolved: 25/Jul/23

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

Type: Task Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLTEST-24 ContentApp provides facility to asser... Selected
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Migrate configuration app
Team: Nucleus

 Description   
  • all functionality should be already available in JCR browser app (mostly copy/paste of its app descriptor)
    • limit the new app to /server config only
    • Download as YAML action will be moved to def. app as CFGUI-103
    • locale the new app into a non deprecated module (e.g. admincentral instead of the old ui-admicentral)


 Comments   
Comment by Dominik Maslanka [ 18/Jul/23 ]

Due to change with architecture approach and starting MX initiative - migration of apps become obsolete

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