Error message for the website admin when trying to add a review Magento 2.3

[jessicana]

Magento 2.3 admin receives an error message when trying to add a review and the stars rating is unavailable. I suppose the stars issue was in Magento 2.2.6 and continues to be unresolved.

Preconditions (*)

1. Magento 2.3
2. PHP 7.1.22

Steps to reproduce (*)

1. Sign in to Magento backend.
2. Marketing > Reviews > New Review
3. Select a product to review

Expected result (*)

1. Admin must be able to add a review
2. A review window should show the nick name, summary of review, STARS and review
3. Rating isn't Available

Actual result (*)

1. The admin gets this message: A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.
2. Have a look at the picture below:
   
   Product review settings:
   Go to Stores > Settings > Configuration
   Under Catalog, select Catalog.

[magento-engcom-team]

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

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

• yes
• no

[magento-engcom-team]

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

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

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

[jignesh26]

@jessicana, Thank your for the issue. I am checking the issue. its showing the error message , i am checking that but for your note you can still submit the review from the admin.

[magento-engcom-team]

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

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

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

[suneet64]

Hi Guys,

This issue is replicable on the clean installation of Magento 2.3 and I have resolved it under the #20146 pull request.

[milindsingh]

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

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

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

[eduard13]

Wasn't able to reproduce this one on the latest version.

Most probably was fixed in scope of #20146.
Closing this one as not being actual anymore.
Thank you.