REST API order info -> "parent" products sku inconsistency with product_id

[tsoftp]

Preconditions (*)

1.Magento 2.4-develop
2.Using Luma test sample data
3.Using Postman for REST API calls.

Steps to reproduce (*)

1.Simply create an order with a configurable product (i.e. a shirt size M color grey or something like that)
2.Make a REST API call to return that order/list of orders.

Expected result (*)

1. Receive the API response for the order.
2. The product I ordered is listed in the "Items" array and its "parent_item" attribute shows the original configurable product's data.

Actual result (*)

1. The product I ordered is listed in the "Items" array and its "parent_item" attribute shows the child's "sku" attribute instead of the sku of the parent_item.

In other words it says that the parent's Sku is the same as the simple product sku which is simply not true, despite it having the correct "name" and "item_id" attribute values.

2. Example info attached with what I am describing happening. File has comments on the lines I'm talking about.
   bug.txt

Thank you!

[magento-engcom-team]

Hi @tsoftp. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@tsoftp do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[tsoftp]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @tsoftp. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @tsoftp, here is your Magento instance.
Admin access: https://i-21231-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @tsoftp. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @tsoftp, here is your Magento instance.
Admin access: https://i-21231-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[tsoftp]

I just reproduced it on the first instance @magento-engcom-team created. (2nd instance I created by accident by quoting him/it)

@tsoftp do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[ryandiamond23]

@magento-engcom-team give me 2.2.7 instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @ryandiamond23, here is your Magento instance.
Admin access: https://i-21231-2-2-7.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.