[MGNLDAM-852] Filters in new asset chooser do not apply Created: 05/Jun/20  Updated: 12/Mar/21  Resolved: 29/Jun/20

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

Type: Bug Priority: Neutral
Reporter: Šimon Demočko Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3h 38m
Original Estimate: Not Specified

Issue Links:
Issue split
split to MGNLDAM-853 Allow filtering on Asset API level Closed
split to MGNLDAM-854 Introduce JCR implementation of the A... Closed
dependency
depends upon MGNLDAM-853 Allow filtering on Asset API level Closed
duplicate
duplicates MGNLDEMO-339 Dialogs do not offer DAM search Open
supersession
supersedes MGNLDAM-632 AssetQuery builder is ignoring keywor... Closed
supersedes MGNLDAM-853 Allow filtering on Asset API level Closed
supersedes MGNLDAM-854 Introduce JCR implementation of the A... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Migrate apps to new UI framework
Sprint: UI FW 5
Story Points: 5

 Description   

Steps to reproduce

  1. Modify mtk's textImage.yaml http://localhost:8080/.magnolia/admincentral#app:resources:browser;/mtk/dialogs/components/textImage.yaml::
    • form: 
        properties:
          linkField:
            $type: linkField
            chooser:
              workbenchChooser:
                appName: dam-chooser
      
  1. Open new pages-app
  2. Create a page
  3. Add Text and Image 
  4. Click select in the linkfield
  5. Type into any of the column filters

Expected results

Content is filtered

Actual results

Nothing happens

Development notes

Some of the Asset providers may not support filtering and requesting support for each may take some time. We can do it on the UI end with the fetched content.

Provide a default implementation method in Asset API interface - the default would filter results in memory, implementors would ideally do filtering on their side.


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