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.

Sign up for GitHub

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

Jump to bottom

[Cloud] Import of customizable options not working #37598

Closed
github-jira-sync-bot opened this issue Jun 9, 2023 · 4 comments
Closed

[Cloud] Import of customizable options not working #37598

github-jira-sync-bot opened this issue Jun 9, 2023 · 4 comments
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.

Comments

@github-jira-sync-bot
Copy link

github-jira-sync-bot commented Jun 9, 2023 •
edited
Loading

Steps to reproduce

  • Go to Stores > All Stores > and set up a multi-store instance (1 website with 2 store views)
  • Go to Catalog > Products and create 2 products with Customizable Options
  • In each product, add a Customizable Option
  • Switch to the second store view, and modify the product name on each product
  • Go to System > Data Transfer > Export and export your 2 products
  • Download the CSV file
  • Go to System > Data Transfer > Import and re-import the file
  • Check both products

Actual results

When importing products with Customizable Options, the options data is lost

Expected results

You should be able to import products with Customizable Options without losing the options data
@github-jira-sync-bot github-jira-sync-bot added Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Jun 9, 2023
@github-jira-sync-bot
Copy link
Author

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-2028

@m2-assistant
Copy link

m2-assistant bot commented Jun 9, 2023

Hi @github-jira-sync-bot. 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:

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.

@github-jira-sync-bot github-jira-sync-bot added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress and removed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: ready for dev labels Jun 19, 2023
@glo23503
Copy link
Contributor

Internal team is working on it.

@github-jira-sync-bot github-jira-sync-bot added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. and removed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Aug 14, 2023
@chittima
Copy link
Contributor

Here is the commit id: fb625cf

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
High Priority Backlog
Status: Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chittima @github-jira-sync-bot @glo23503