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

Dashboard Most Viewed Products Tab in admin - prices issue #5660

Closed
farior opened this issue Jul 15, 2016 · 7 comments
Closed

Dashboard Most Viewed Products Tab in admin - prices issue #5660

farior opened this issue Jul 15, 2016 · 7 comments
Assignees
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@farior
Copy link

farior commented Jul 15, 2016

Steps to reproduce

  1. Make a few configurable products
  2. Give some price to configurations
  3. View this products
  4. Go to admin area

Expected result

  1. Most Viewed Products tab should display correct prices for products

Actual result

  1. Prices for products in Most Viewed Products tab are obtained from configurable product
  2. 86e7ed5232

Product views is stored in report_event table with configurable product ID's
Since we have no opportunity to change configurable product price, this prices will never update

@antboiko
Copy link

Hi @farior , thanks for reporting this. We've created internal ticket MAGETWO-56014.

Thanks,
Anton.

@antboiko antboiko added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development PS bug report labels Jul 27, 2016
@vkorotun vkorotun removed the PS label Aug 4, 2016
@farior
Copy link
Author

farior commented Jan 30, 2017

Any update on this?

mmansoor-magento pushed a commit that referenced this issue Feb 17, 2017
Bug fixes:
* MAGETWO-56014: [GitHub] Dashboard Most Viewed Products Tab in admin - prices issue #5660
* MAGETWO-62044: Not possible to update or delete products in cart or checkout after deleting address
@magicbunneh
Copy link
Contributor

Fix for this issue was merged:

@veloraven
Copy link
Contributor

Closed.
This issue was already fixed for develop branch.
It should be fixed soon for previous versions.
Internal ticket for ver. 2.0 - MAGETWO-64144
Internal ticket for ver. 2.1 - MAGETWO-63818

@korostii
Copy link
Contributor

korostii commented Jun 19, 2017

I've heard closed tasks are not being monitored by the Community Engineering team no more, see here. Does that mean these internal tickets for 2.0 and 2.1 won't be a priority neither?

If that the case, could you please keep the issue open? It would be a pity to see it being forgotten about, and lost, and reported again.

@veloraven
Copy link
Contributor

@korostii I will not reopen this issue but we have the new one with the same problem but better description - #9768. It will stay open for now.

@korostii
Copy link
Contributor

korostii commented Jul 4, 2017

Thanks @veloraven, glad to hear that.

slavvka pushed a commit that referenced this issue May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

6 participants