Inverted attribute grid system column

[elevinskii]

Description

The Pull Request fixes small issue in product attribute grid Catalog > Products > Product Page > Add Attribute, where System column should be inverted instead displaying as is.

The System grid column is related with is_user_defined column in table, and when is_user_defined = 0 then System should be Yes and vice versa.

Manual testing scenario

1. Create new product attribute - Stores > Attributes > Product > Add New Attribute
2. Make sure that in Stores > Attributes > Product grid System column for the newly created attribute displayed as No
3. Go to any backend product page and open modal attribute grid - Catalog > Products > Product Page > Add Attribute
4. Make sure that System column is also as No there

The fix has been covered by MFTF test.

Resolved issues:

1. resolves [Issue] Inverted attribute grid system column #30235: Inverted attribute grid system column

[m2-assistant]

Hi @elevinskii. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[elevinskii]

@magento run all tests

[sidolov]

@magento create issue

[orlangur]

@magento run all tests

[elevinskii]

@magento run all tests