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

[Issue] [MFTF] add new AdminOpenConfigurationStoresPageActionGroup #29848

Closed
m2-assistant bot opened this issue Aug 31, 2020 · 1 comment · Fixed by #29827
Closed

[Issue] [MFTF] add new AdminOpenConfigurationStoresPageActionGroup #29848

m2-assistant bot opened this issue Aug 31, 2020 · 1 comment · Fixed by #29827
Assignees
@Usik2203
Labels
Component: Backend Component: Tinymce Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Priority: P3 May be fixed according to the position in the backlog. Progress: done 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 Aug 31, 2020

This issue is automatically created based on existing pull request: #29827: [MFTF] add new AdminOpenConfigurationStoresPageActionGroup

This PR add new AdminOpenConfigurationStoresPageActionGroup and use this one instead
<amOnPage url="{{ConfigurationStoresPage.url}}" stepKey="navigateToWYSIWYGConfigPage1"/>
<waitForPageLoad stepKey="wait1"/>
@m2-assistant m2-assistant bot added Component: Backend Component: Tinymce Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Aug 31, 2020
@Usik2203 Usik2203 mentioned this issue Aug 31, 2020
Merged
1 task
@ghost ghost assigned Usik2203 Aug 31, 2020
@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Aug 31, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR in progress labels Sep 24, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Sep 24, 2020
@magento-engcom-team magento-engcom-team added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Sep 25, 2020
@magento-engcom-team
Copy link
Contributor

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

The fix will be available with the upcoming 2.4.2 release.

@m2-community-project m2-community-project bot added Progress: done and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Sep 25, 2020
@sdzhepa sdzhepa mentioned this issue May 10, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Usik2203 Usik2203

Labels
Component: Backend Component: Tinymce Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Priority: P3 May be fixed according to the position in the backlog. Progress: done Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Low Priority Backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[MFTF] add new AdminOpenConfigurationStoresPageActionGroup Usik2203/magento2
2 participants
@Usik2203 @magento-engcom-team