[MGNLUI-6251] New JCR Browser App: Do use 'website' workspace as default and not 'config' Created: 29/Sep/20  Updated: 04/Jan/21  Resolved: 04/Jan/21

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

Type: Improvement Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-6489 JCR-Browser: Renaming of properties f... Closed
duplicate
duplicates MGNLUI-6441 JCR app should default to website wor... Closed
relation
is related to MGNLUI-6012 JCR Browser App: Please make workspac... Open
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)
Epic Link: Migrate JCR Browser

 Description   

Situation:

The new 'jcr-browser-app' (coming with M6.2.3) uses 'config' as its default workspace, and not 'website' anymore. 
Configured on the jcr-datasource.

Problem:

  • Developers (front-end & back-end) using the JCR-Bowser are by far more interested in the 'website' workspace than in the 'config' workspace. Checking dialog saves etc.
  • The 'Configuration' App already shows everything except the meta data... And checking the meta data in 'config' workspace is suuuper rare.
  • Less and less configurations are in the config workspace, not much to check there.

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