Closed Bug 617202 Opened 14 years ago Closed 14 years ago

User reply counts remain at zero

Categories

(support.mozilla.org :: Army of Awesome, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rbillings, Unassigned)

Details

The tweet counts for all users remains at zero even after the user makes multiple Army of Awesome replies.

1) log in as user1
2) select AoA tweet> submit reply
3) view tweet reply and user reply count

expected: user reply count increases
actual: always displays at zero
So the issue seems to be that '0 replies' always shows until any user replies. At that point X replied displays- but it never shows an actual total of replies other than the initial zero state.
This is currently by design. If showing reply counts on *replies* is confusing, we can remove them in a future release.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
If I understand this right, I'm fixing this as part of bug 617347. That is, replying to a tweet that has 1 reply already will put something like "You and 1 other replied" next to it.
(In reply to comment #3)
> If I understand this right, I'm fixing this as part of bug 617347. That is,
> replying to a tweet that has 1 reply already will put something like "You and 1
> other replied" next to it.

Exactly
Fixed as part of http://github.com/jsocol/kitsune/commit/4ee4764.
Status: VERIFIED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: WONTFIX → FIXED
Tentatively moving this to 2.4 since it didn't make it in 2.3.2.

James, when would you like these Army of Awesome fixes to be released? Also applies to bugs 617347 and 617489.
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: 2.3.2 → 2.4
(In reply to comment #6)
> Tentatively moving this to 2.4 since it didn't make it in 2.3.2.

Yeah, this got checked in with the fix to bug 617347, so it will go out in 2.4.
Verified replied link shows up immediately now- nice!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.