[MGNLDAM-935] Expand root folder in assets chooser default if there is one provider Created: 03/Nov/20  Updated: 24/Jun/21  Resolved: 04/Feb/21

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.6

Type: Improvement Priority: Neutral
Reporter: Jürgen Brömmer Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: ux-improvement, ux-improvement-selected
Remaining Estimate: Not Specified
Time Spent: 0.45h
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-11-03 at 13.26.06.png     PNG File image (1).png     PNG File image-2020-11-03-10-37-59-365.png    
Issue Links:
Cloners
is cloned by MGNLDAM-936 Magnolia Assets provider label should... Open
causality
duplicate
duplicates MGNLDAM-915 DAM Chooser should not show a provide... Closed
relation
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)
Release notes required:
Yes
Date of First Response:
Epic Link: Migrate Assets
Sprint: UI FW 21
Story Points: 2

 Description   

Current:

When using this dialogue repetitively (e.g. when adding several assets) one gets pretty annoyed when the node has to be reopened every. single. time.

 

 
Improvement:

  • provider column should show 'Magnolia assets' instead of 'JCR'
  • If there's only one provider:
    • hide root folder (JCR) and show only child folders (same as we already do it in the app)
  • If external DAM integrated
    • rename root folder 'JCR' to 'Magnolia assets'

 



 Comments   
Comment by Šimon Demočko [ 21/Jan/21 ]

Devs raised concern over the name "Magnolia Assets", since all assets viewed in Magnolia are considered Magnolia.

Comment by Richard Gange [ 24/Mar/21 ]

What happens if you only have "Magnolia Assets"? Do I still see the folder?

Comment by Roman Kovařík [ 29/Mar/21 ]

Nope

Generated at Mon Feb 12 05:04:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.