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.

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

I am having the exact same problem as described above! I am using magento 2.2.5! #18253

Closed
sourabh2yadav opened this issue Sep 26, 2018 · 10 comments
Labels
Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed

Comments

@sourabh2yadav
Copy link

sourabh2yadav commented Sep 26, 2018

The only difference that i can see between the products that exportet fine and the ones that have dublicates is the field "custom_options" - it looks like prducts with custom options get wrong export with dublicate products
ipmsgclip_r_1537949793_0

image

Originally posted by @simonmaass in #7350 (comment)

@magento-engcom-team
Copy link
Contributor

Hi @sourabh2yadav. 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 $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Sep 26, 2018
@ghost ghost self-assigned this Sep 26, 2018
@magento-engcom-team
Copy link
Contributor

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

    DetailsIf 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

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

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

@ghost
Copy link

ghost commented Sep 26, 2018

Hi @sourabh2yadav Thank you for you report, this issue already fixed in 2.2-develop branch.

@ghost ghost closed this as completed Sep 26, 2018
@sourabh2yadav
Copy link
Author

Hi @sourabh2yadav Thank you for you report, this issue already fixed in 2.2-develop branch.

Could you please provide me link for the solution.

@zulus
Copy link

zulus commented Oct 12, 2018

I have this on 2.2.6, so I have to wait for 2.2.7 ?

@zulus
Copy link

zulus commented Dec 14, 2018

Knock knock? Is this part of 2.2.7 or I have to upgrade to 2.3.0?

@simonmaass
Copy link

I am still having this issue in 2.2.7

@sarfarazbheda
Copy link
Contributor

We are still facing issue with 2.2.7. Is there any solution?

@sarfarazbheda sarfarazbheda reopened this Feb 7, 2019
@ghost
Copy link

ghost commented Feb 7, 2019

@sourabh2yadav the duplicate rows is expected behavior, this is non-issue, if you have 1 product in 2 websites or store view, the second row is product with the same sku for second store-view.

selection_294

@ghost ghost closed this as completed Feb 7, 2019
@ghost
Copy link

ghost commented Feb 7, 2019

@sarfarazbheda also please look this pr -> #19786 maybe problem casued by this issue.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed
Projects
None yet
Development

No branches or pull requests

5 participants