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: Admin Delete CMS Block Test #30372

Closed
m2-assistant bot opened this issue Oct 8, 2020 · 1 comment · Fixed by #30359
Closed

[Issue] MFTF: Admin Delete CMS Block Test #30372

m2-assistant bot opened this issue Oct 8, 2020 · 1 comment · Fixed by #30359
Labels
Component: Cms Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.4.0 Indicates original Magento version for the Issue report. 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 Oct 8, 2020

This issue is automatically created based on existing pull request: #30359: MFTF: Admin Delete CMS Block Test


Description
This PR contains a test for deleting CMS block from grid by Admin User

Steps To reproduce:

1 - Create CMS block
2 - Login as Admin User
3 - Navigate to Content->Blocks
4 - Find Created CMS Block
5 - Delete Created CMS Block
6 - Perform Assertions

@m2-assistant m2-assistant bot added Component: Cms 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 Oct 8, 2020
@m2-community-project m2-community-project bot added this to Ready for Grooming in Low Priority Backlog Oct 8, 2020
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Pull Request In Progress in Low Priority Backlog Oct 8, 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 Oct 8, 2020
engcom-Foxtrot added a commit to DmitryTsymbal/magento2 that referenced this issue Oct 27, 2020
@ghost ghost unassigned DmitryTsymbal Nov 2, 2020
@ghost ghost added Progress: PR in progress and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Nov 2, 2020
@gabrieldagama gabrieldagama added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Nov 9, 2020
@gabrieldagama
Copy link
Contributor

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #30359 by @DmitryTsymbal 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 moved this from Pull Request In Progress to Done in Low Priority Backlog Nov 9, 2020
@m2-community-project m2-community-project bot moved this from Done to Pull Request In Progress in Low Priority Backlog Nov 9, 2020
@sdzhepa sdzhepa added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Nov 11, 2020
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in Low Priority Backlog Nov 11, 2020
@magento-engcom-team magento-engcom-team added Reported on 2.4.0 Indicates original Magento version for the Issue report. and removed Reported on 2.4.x Indicates original Magento version for the Issue report. labels Nov 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Cms Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.4.0 Indicates original Magento version for the Issue report. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Development

Successfully merging a pull request may close this issue.

4 participants