Last modified: 2014-09-08 12:27:45 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 T70790, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68790 - Always send notification to the user being replied to
Always send notification to the user being replied to
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-29 07:47 UTC by Erik Bernhardson
Modified: 2014-09-08 12:27 UTC (History)
7 users (show)

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


Attachments

Description Erik Bernhardson 2014-07-29 07:47:14 UTC
Recent changes have made so only users watchlisting a topic get notified that a reply has happened.  Should also notify the user being replied to.
Comment 1 Danny Horn 2014-07-29 16:59:42 UTC
in backlog: https://trello.com/c/Ucgzd76H
Comment 2 Matthias Mullie 2014-08-20 10:01:21 UTC
Well, should we send a notification to the author of the parent post of the new reply? Due to our limited threading depth, the reply's parent may actually *not* be the one you replied to (if it was already at max depth)

To illustrate:

    Post 1
        > Post 2, in reply to post 1
            > Post 3, in reply to post 2 (this is at max depth)
            > Post 4, in reply to post 3 (but really, it's a reply to post 2,
          since 3 was already at max depth)

Also: when someone creates a topic/post, he's automatically subscribed. Not being subscribed at this point is a choice (has to actually unsubscribe). I assume if someone's chosen not to subscribe, we may rather not want to keep bugging him/her with notifications for new replies?

Related: we still have notifications for users that are mentioned, and if someone clicks "reply", [[User:Username]] is already prefilled. (related: I just noticed that when subscribed + when mentioned, 2 notifications are sent; do we want that?)
Comment 3 Danny Horn 2014-08-22 18:18:07 UTC
That's a good question. If somebody's chosen to unsubscribe, that probably means they don't want notifications about it. Maybe we should ping Nick, and see what he thinks?

In general, I'd say we don't want two notifications for the same action. A "you were mentioned" notification is probably a stronger incentive to click, so we may want to treat the general "somebody responded to this topic" as a duplicate. 

The problem is: we're doing roll-ups with the general "somebody responded". So if three people responded on the thread, but one of them mentioned you, what do we show? I think this is a design review discussion; I'll bring it up there...
Comment 4 Jon 2014-09-08 12:27:45 UTC
Bugs should be actionable and this one isn't. Nick/Danny can you chat with design raise a new bug explaining the desired behaviour?

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


Navigation
Links