Magento Community Edition: Version 2.4.5 - Export Product CSV have unwanted values in "additional_image_labels" column

[RocktechnolabsDev]

Preconditions and environment

1. Magento Community Edition 2.4.5 without sample data is installed.
2. Website have products

Issue:

• Project have single website setup
• Single product have multiple images setup into product, eg. one product image set as Base, Swatch another one as Thumbnail and so on...

Export the products from backend export section, Exported Product CSV have unwanted values in "additional_image_labels" column

Steps to reproduce

1. Login into admin > System > Data Transfer > Export
2. Select "Products" option from Entity Type drop down.
3. Leave other configuration as it is, Click on continue and wait while file is export.
4. Once file is exported, Download product csv file from the grid.
5. Open the downloaded CSV file, check "additional_image_labels" column value

Please check attachments for your reference.

Expected result

"additional_image_labels" column is empty

Actual result

"additional_image_labels" column is filled with unwanted values.

Additional information

No response

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

Hi @UtsavRock1811. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.

⚠️ According to the Magento Contribution requirements, all issues 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 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.

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

[m2-assistant]

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).

  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.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.

[pemann]

@magento give me 2.4.5 instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @pemann, here is your Magento Instance: https://f86db232f65248aad41a229f0f5e35d7.instances.magento-community.engineering
Admin access: https://f86db232f65248aad41a229f0f5e35d7.instances.magento-community.engineering/admin_2ce2
Login: b39c99db
Password: 933a52a31b63

[engcom-November]

Hi @UtsavRock1811 ,
Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop instance and the issue is reproducible. Hence confirming the issue.

[github-jira-sync-bot]

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