[MGNLUI-6762] App launcher UX improvements in SaaS Created: 24/Jun/21 Updated: 23/Jan/23 Resolved: 12/Oct/22 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0 |
| Type: | Epic | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Epic Name: | applauncher-improvements | ||||||||||||
| Acceptance criteria: |
[ ]*
!!!TODO!!!: this issue was converted to epic from a simple story, the AC entries below need to be extracted into their own issues!
[ ]*
check whether non-CT bound apps appear on the app launcher fine (and vanish when the definition is gone).
[ ]*
it is verified that the CT-powered content app reflects the changes of the related CT definition transparently to the user (should be covered by the existing functionality, and the tests!)
[ ]*
app launcher configuration is config env sensitive and I always see only those aps that are relevant to the current state of the app descriptor registry in my environment.
[ ]*
AdminCentral reacts on the environment switch and actualises the UI (possibly restarting or closing the apps)
[ ]*
users can define app launcher layout per environment. However, the system app launcher layout "skeleton" remains present in the system and can be used a default. Current approach: one can decorate the "stock" app launcher layout that we provide.
|
||||||||||||
| Story Points: | 13 | ||||||||||||
| Description |
|
End goal:
|