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.

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

[Issue] [MFTF] Updating with AdminOpenCMSPagesGridActionGroup #31573

Closed
m2-assistant bot opened this issue Jan 6, 2021 · 1 comment · Fixed by #31569
Closed

[Issue] [MFTF] Updating with AdminOpenCMSPagesGridActionGroup #31573

m2-assistant bot opened this issue Jan 6, 2021 · 1 comment · Fixed by #31569
Assignees
Labels
Component: Catalog Component: Cms Component: Widget Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.

Comments

@m2-assistant
Copy link

m2-assistant bot commented Jan 6, 2021

This issue is automatically created based on existing pull request: #31569: [MFTF] Updating with AdminOpenCMSPagesGridActionGroup


Description (*)

Test have been updated with AdminOpenCMSPagesGridActionGroup

@m2-assistant m2-assistant bot added Component: Catalog Component: Cms Component: Widget Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jan 6, 2021
@gabrieldagama
Copy link
Contributor

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #31569 by @AnnaAPak in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.3 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Catalog Component: Cms Component: Widget Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Status: Pull Request In Progress
Development

Successfully merging a pull request may close this issue.

2 participants