In Backend, default store values for product attributes instead of admin values

[FloForMagento]

Preconditions and environment

Adobe Commerce ver. 2.4.5-p8

Steps to reproduce

1. Go to Store, Attributes Product, select one attribute (eg: color), set Default Store view value for an option, different from the admin one. Save attribute.

2. Go to Marketing, Cart Price Rules, Add new rule. Under Conditions, clic on plus, select "Product attribute combinaison". Clic on the plus to select the attribute edited in step 1, color for my exemple.

Expected result

In Backend, attributes should use admin values. So for my exemple, I should see Black.

Actual result

Default store values are used instead of admin values.

Additional information

The point of Admin values is to be used in Backend. Typically thoses would be unique code values, while in Default store view you likely want label intented for customers, not necessary unique.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @FloForMagento. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. 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: :point_down:

• [ ] 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[FloForMagento]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @FloForMagento. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @FloForMagento, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[benjamin-volle]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @benjamin-volle. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @benjamin-volle, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[FloForMagento]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @FloForMagento. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @FloForMagento, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Bravo]

Hi @FloForMagento,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Default store values are used instead of admin values.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-13048 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[glo23503]

Adobe Commerce Engineering team started working on this issue. For now, you can pause work on this PR. We will notify once the issue is fixed. Please leave comments for any further questions. Thank you!