Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce Used In Blocks filter #1468

Closed
gabrieldagama opened this issue Jun 15, 2020 · 3 comments · Fixed by #1593
Closed

Introduce Used In Blocks filter #1468

gabrieldagama opened this issue Jun 15, 2020 · 3 comments · Fixed by #1593
Assignees
@sivaschenko
Labels
Backend Frontend/UI Priority: P2 Should be fixed as early as possible
Milestone
2.1.0

Comments

@gabrieldagama
Copy link
Contributor

gabrieldagama commented Jun 15, 2020 •
edited
Loading

Story #1291

Add a filter to allow users to filter assets that are used in specific blocks. The input will display blocks that exist on the platform and have a field for search by block title, the user must be able to select/filter multiple blocks at the same time. The input should be similar to the one used on product edit form to select categories, but without the hierarchy tree.

Screenshot 2020-06-17 at 10 17 47

Technical details
https://github.com/magento/adobe-stock-integration/wiki/MediaGalleryUi-DataProvider
@m2-assistant
Copy link

m2-assistant bot commented Jun 15, 2020

Hi @gabrieldagama. Thank you for your report.
To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this

@gabrieldagama gabrieldagama changed the title Introduce User In Blocks filter Introduce Used In Blocks filter Jun 15, 2020
@lenaorobei lenaorobei added this to the 2.1.0 milestone Jun 16, 2020
@gabrieldagama gabrieldagama added Priority: P2 Should be fixed as early as possible Severity: S2 Affects non-critical data or functionality and forces users to employ a workaround Backend Frontend/UI Progress: ready for dev and removed Severity: S2 Affects non-critical data or functionality and forces users to employ a workaround has dependency labels Jun 17, 2020
@ghost ghost self-assigned this Jun 29, 2020
@ghost
Copy link

ghost commented Jun 29, 2020

@magento I am working on this

@m2-assistant
Copy link

m2-assistant bot commented Jun 29, 2020

Hi @gregbalonzo! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

@ghost ghost mentioned this issue Jun 30, 2020
Closed
@m2-community-project m2-community-project bot unassigned ghost Jul 7, 2020
@sivaschenko sivaschenko mentioned this issue Jul 12, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sivaschenko sivaschenko

Labels
Backend Frontend/UI Priority: P2 Should be fixed as early as possible
Projects
None yet
Milestone
2.1.0
3 participants
@sivaschenko @gabrieldagama @lenaorobei