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

Product customizable options issue #20497

Closed
eduard13 opened this issue Jan 23, 2019 · 11 comments
Closed

Product customizable options issue #20497

eduard13 opened this issue Jan 23, 2019 · 11 comments

Comments

@eduard13
Copy link
Contributor

@eduard13 eduard13 commented Jan 23, 2019

Preconditions (*)

  1. Magento 2.3-develop

Steps to reproduce (*)

  1. Open the product page (new or existing one) in Admin Panel
  2. Add several new Customizable Options

Expected result (*)

  1. The new added options should have a bottom border, for having a good look
    xnip2019-01-23_12-05-33

Actual result (*)

  1. The border is missing for the customizable options
    xnip2019-01-23_12-00-08
@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Jan 23, 2019

Hi @eduard13. 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.

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

  • yes
  • no
@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Jan 23, 2019

Hi @irajneeshgupta. 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.

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Jan 23, 2019

Hi @vasilii-b. 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.

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Jan 23, 2019

@irajneeshgupta Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97882 were created

@irajneeshgupta irajneeshgupta removed their assignment Jan 23, 2019
@vasilii-b vasilii-b removed their assignment Jan 23, 2019
@rogyar

This comment has been minimized.

Copy link
Contributor

@rogyar rogyar commented Jan 23, 2019

@irajneeshgupta thank you for the confirmation. Does it really take 1 minute for you to reproduce the issue?

@irajneeshgupta

This comment has been minimized.

Copy link
Member

@irajneeshgupta irajneeshgupta commented Jan 23, 2019

@irajneeshgupta thank you for the confirmation. Does it really take 1 minute for you to reproduce the issue?

@rogyar
yeah, i have local setup of dev-2.3-develop , it takes hardly 1 min to view an item and click on Customizable Options ->add options.

@eduard13
I assumed that it will take sometime to create PR of it.

@engcom-backlog-nazar

https://i-20487-2-3-develop.instances.magento-community.engineering/admin
all 2.3-develop instance are redirecting to 2.2-develop instance.

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Jan 29, 2019

Hi @eduard13. Thank you for your report.
The issue has been fixed in #20498 by @eduard13 in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.1 release.

@dmytro-ch

This comment has been minimized.

Copy link
Contributor

@dmytro-ch dmytro-ch commented Feb 11, 2019

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

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Feb 11, 2019

Hi @dmytro-ch. Thank you for your request. I'm working on Magento 2.2-develop instance for you

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Feb 11, 2019

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

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Feb 12, 2019

Hi @eduard13. Thank you for your report.
The issue has been fixed in #20821 by @eduard13 in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.9 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.