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] fixed the block names in an admin form #39701

Open
5 tasks
m2-assistant bot opened this issue Mar 4, 2025 · 1 comment · May be fixed by #39660
Open
5 tasks

[Issue] fixed the block names in an admin form #39701

m2-assistant bot opened this issue Mar 4, 2025 · 1 comment · May be fixed by #39660
Labels
feature request Reported on 2.4.x Indicates original Magento version for the Issue report.

Comments

@m2-assistant
Copy link

m2-assistant bot commented Mar 4, 2025

This issue is automatically created based on existing pull request: #39660: fixed the block names in an admin form


Noticed the admin product attribute form layout has mistyped block names for Manage Options (Values of Your Attribute) and Advanced Attribute Properties in the product attribute form. Just fixed the block names appropriately.

New-Product-Attribute-Product-Attributes-Attributes-Stores-Magento-Admin-02-26-2025_08_49_PM

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
@m2-assistant m2-assistant bot linked a pull request Mar 4, 2025 that will close this issue
6 tasks
@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Mar 4, 2025
@engcom-November engcom-November self-assigned this Mar 7, 2025
Copy link
Author

m2-assistant bot commented Mar 7, 2025

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Reported on 2.4.x Indicates original Magento version for the Issue report.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants