453128 - Reviews listed on main add-on page should indicate if they have developer replies

Status: VERIFIED FIXED

(addons.mozilla.org Graveyard :: Public Pages, enhancement, P3)

Description

[R Pruitt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17pre) Gecko/20080716 K-Meleon/1.5.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

Currently, two of the three reviews on the front page have developer replies, but they don't show up unless the user goes to the reviews page.

Reproducible: Always

Steps to Reproduce:
1. Go to URL: https://addons.mozilla.org/en-US/firefox/addon/629.
2.
3.
Actual Results:  
No developer reply for reviews on front page.

Expected Results:  
Developer reply on front page.

Comment 1

[Fred Wenzel [:wenzel]]

Hm. I'd rather not clutter the details page. However, we could indicate/link to it; this would make this bug depend on bug 440453.

Comment 2

[R Pruitt]

Personally, I'd also be happy if reviews with developer replies were shunted from the front page to the review page, but presume this would be more difficult.

It would be nice to avoid having [factually incorrect/issues specific to a single user] reviews on the front page appearing to have no reply.

Comment 3

[David McRitchie]

Hopefully the developer would take the hint to improve AMO documentation, but this is where critical information is often found.  It is the developer comments that I consider most important.  Currently the developer is the only one who can make comments without a rating, and they are not shown even though almost certainly more important than the rated comments.

Comment 4

[Dave Garrett]

Unless there are any objections, I'll rename this and confirm based on comment 1.

Just adding a link to the developer reply makes sense. It would hopefully cut down on repeat complaints in reviews if users could just see that there was already an answer given to the previous complaint. (that probably shouldn't have been in a review anyway)

This could be done without bug 440453 by just linking to the review page and not the reply within it. Seeing as only the top 3 reviews are shown on the front page the reply will be near the top and easy enough to find.

Comment 6

[Dave Garrett]

As far as I'm concerned the current developer reply system is borderline-useless right now. People have no clue that a review has been replied to, which leads to more confused users (even though they shouldn't really be asking questions here). The same confusion pops up again in more reviews, occasionally even multiple reviewers arguing amongst themselves.

A simple "read developer reply" link (possibly w/ an icon) in the lower right of the box for a review on the front page is very much needed here, at a minimum.

Comment 7

[Seth Wagoner]

I strongly agree that there's a problem to be addressed here. 

I would suggest that developer replies on the front page unfold inline as do multiple reviews from the same reviewer on the reviews page (a suggestion of mine that was implemented by Les Orchard, so perhaps he would be able to make it happen fairly easily in this case as well).

Comment 8

[Dave Garrett]

Yes, that would be quite nifty and avoid dependence on bug 440453.

Comment 10

[fcp]

I agree to the entire comment #6 by Dave, but in my opinion the problem is even more serious than explained in this bug.
(In reply to comment #6)
> People have no clue that a review has been replied to,
I am afraid that most people have no clue that a review *can* be replied to.  In other words, most AMO users, including developers (!), simply do not know that AMO allows developers to reply to reviews at all.  In fact, when I found the link labeled “reply,” it was just by chance.

Comment 11

[Jorge Villalobos [:jorgev] (he/him)]

Giving this more attention based on votes and activity.
I also agree that the review page is somewhat obscure. It's hard to discover you can reply to reviews, or flag them for moderation. It'd be good to include this as another way to discover the usefulness of that page.

Comment 12

[fcp]

If you want the link to developer replies and cannot wait for someone to fix this bug, see a user script at http://userscripts.org/scripts/show/69660.

Comment 13

[fcp]

By the way, it is not strictly necessary to depend on bug 384798 (or its dupe bug 440453) even if we want to provide the links to developer replies, because the reviews shown on the add-on details page are newest three and they are always on the first page of reviews.  It might be cleaner to use permalinks, though.

Anyway I am changing the dependence from 440453 to 384798.

Comment 16

[Justin Scott [:fligtar]]

Let's do this soon with the new reviews sytem. If a review shown on the details page has a developer reply, there should be a link similar to the previous reviews link that goes to the thread page.

text:
Show the developer's reply to this review

Comment 17

[3e2224c2]

I agree. Developer replies should be displayed on front page. I have extensions with comments about bugs that have already been fixed two versions before and bad reviews because the user failed to understand the extension is not compatible with his OS. We should be able to address those issues in the front page, so other users don't feel the extension doesn't work properly.

Comment 18

[Jeff Balogh (:jbalogh)]

http://github.com/jbalogh/zamboni/commit/d4f61cf

Comment 19

[krupa raj[:krupa]]

verified 

for add-ons:
https://next.addons.mozilla.org/en-US/firefox/addon/3456/#reviews

for personas:
https://next.addons.mozilla.org/en-US/firefox/addon/216089/#reviews