Last modified: 2013-12-12 19:36:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59864, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57864 - Flow: duplicate notifications when replying directly to someone
Flow: duplicate notifications when replying directly to someone
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-02 18:41 UTC by Maryana Pinchuk
Modified: 2013-12-12 19:36 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Maryana Pinchuk 2013-12-02 18:41:44 UTC
When I reply directly to a user (not to the topic), that user gets 2 notifications: 1 reply notification and 1 mention notification. 

We should only be sending the 1 reply notification.
Comment 1 Bingle 2013-12-02 18:48:45 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/556, but people from the community are welcome to contribute here and in Gerrit.
Comment 2 bsitu 2013-12-05 22:15:51 UTC
More specifically, This happens when a user replies to a reply and the creator of the reply is also the topic creator
Comment 3 Gerrit Notification Bot 2013-12-06 00:04:47 UTC
Change 99563 had a related patch set uploaded by Bsitu:
Remove duplicated mention notification

https://gerrit.wikimedia.org/r/99563
Comment 4 Gerrit Notification Bot 2013-12-10 23:45:52 UTC
Change 99563 merged by jenkins-bot:
Remove duplicated mention notification

https://gerrit.wikimedia.org/r/99563

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links