Open Bug 1869333 Opened 10 months ago Updated 8 months ago

The Review checker should trigger an auto-update to show real ratings for outdated products rated 1.5 stars or lower

Categories

(Firefox :: Shopping, enhancement, P3)

Desktop
Unspecified
enhancement

Tracking

()

Tracking Status
firefox-esr115 --- disabled
firefox120 --- disabled
firefox121 --- disabled
firefox122 --- affected

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fidefe-shopping])

Found in

  • Nightly 122.0a1 (2023-12-11)

Affected versions

  • Nightly 122.0a1 (2023-12-11)

Affected platforms

  • ALL

Steps to reproduce

  1. Reach an outdated Product details page on amazon that has 1.5 stars or lower
  2. Click the "New info to check Check now" button.

Expected result

  • Reaching a product rated 1.5 stars or lower that also has the Outdated "New info to check" message could show a different Rating after the update.
  • If the Review checker would trigger that update as soon as the user reaches the product details page, even with a lower rating it will show the Analysis in progress message and they might stick around for the latest reviews.
  • After a while because of the update that occurs once every 7 8 days we would always show the updated reviews to our users.
  • This could help sellers who got bad reviews in the past but now have a better rated product
  • The "Analyzing in progress" message would keep the users on the page until the real reviews are displayed instead of seeing the 0.5 stars and immediately moving away to a new product.

Actual result

  • The users will see the 0.5 stars until they manually click the "Check now" button

NOTES: This might not be such a good idea if the increased load on the server would cause performance issues with Firefox.
The bad reviewed products might not be worth it to have this enhancement.

Regression range
N/A

Will, thoughts on priority here?

My sense is that the lowest value products are not worth adding additional server load, but curious what your thoughts are.

As a reminder, the priorities are listed here: https://wiki.mozilla.org/BMO/UserGuide/BugFields#priority

feel free to set the priority directly on the bug, or add your thoughts in a comment and I"ll set the priority

Flags: needinfo?(wrocklin)

I think this one is for the Fakespot team to evaluate. We're more or less the consumer of their product. Adding csluz to the thread.

Flags: needinfo?(wrocklin) → needinfo?(csluz)

I think this is a future enhancement, and would be something we consider on the Fakespot side. I don't know exactly how the Bugzilla process works, but my guess is that this can be closed on this side, and I added it as enhancement possibility on the Fakespot side.

Flags: needinfo?(csluz)
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.