Page MenuHomePhabricator

Special:Log/growthexperiments floods RecentChanges, bothers re-assigned mentee when a mentor resigned
Closed, ResolvedPublicBUG REPORT

Description

A mentor in my project recently resigned from Mentor Project. They followed the instruction from Special:MentorDashboard, removed their name and re-assign their mentees. That's pretty nice except two thing: logs from Special:Log/growthexperiments flooded Special:RecentChanges. (I have to say I was surprised by the huge amounts of relevant log entries)

image.png (222×810 px, 63 KB)

Another issue is that user is unhappy when received notification (especially email!) when they are re-assigned with a new mentor. A user has complained about this bothersome email (although they was assigned to a mentor before T301268 is resolved, but not that relevant).

image.png (320×595 px, 74 KB)

My suggestions:

  • Logs of growthexperiments should be hidden in RecentChanges by default (like bot edits)
  • User should not receive email notifications by default in Special:Preferences#mw-prefsection-echo

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
mewoph added subscribers: Urbanecm_WMF, RHo, mewoph.

@Urbanecm_WMF @RHo — is customization of mentorship-related notifications is in the roadmap for mentor dashboard?

Urbanecm_WMF changed the subtype of this task from "Task" to "Bug Report".

@Urbanecm_WMF @RHo — is customization of mentorship-related notifications is in the roadmap for mentor dashboard?

Thanks for the ping. The logs should be already hidden from recent changes (see code), so this looks like a bug for me. I can confirm by querying the analytics replica that the bot flag was not set for some reason.

AFAIK we don't have any plans to change how mentor reassignment notifications work, but there's a task for it: T298070: Special:QuitMentorship notifications might be disruptive. Maybe we can discuss possible improvements there? I added my thoughts there. @Stang I encourage you to read my comment at the other task – I have a question for you there as well. Thanks!

Hi @Urbanecm_WMF - I agree with @Stang and @Tgr comments on T298070 as well as the suggestions on this one, in that it seems far more disruptive to the majority of newcomers who have low/no contact with their mentor to be told via notifications when their mentor retires or is changed in some way.

Could the notifications be restricted to only being sent to those newcomers who have posted a question to that mentor before in their mentor/help module? That way, we avoid people who have never engaged with Username:Rho2017 being surprised by a "change of mentor" message since they likely won't notice.

Hi @Urbanecm_WMF - I agree with @Stang and @Tgr comments on T298070 as well as the suggestions on this one, in that it seems far more disruptive to the majority of newcomers who have low/no contact with their mentor to be told via notifications when their mentor retires or is changed in some way.

Could the notifications be restricted to only being sent to those newcomers who have posted a question to that mentor before in their mentor/help module? That way, we avoid people who have never engaged with Username:Rho2017 being surprised by a "change of mentor" message since they likely won't notice.

Yes, that should definitely be possible (and personally, I think that's fine. @Stang, would it resolve the issue?

Looks good to me if notification is only shown to those posted a question via mentor module. Thanks!

Change 896045 had a related patch set uploaded (by Msz2001; author: Msz2001):

[mediawiki/core@master] RecentChange: Log entries of not-bots can be internally marked as such

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

Change 897186 had a related patch set uploaded (by Msz2001; author: Msz2001):

[mediawiki/extensions/GrowthExperiments@master] Bulk mentor reassignment won't spam RecentChanges

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

Change 896045 abandoned by Msz2001:

[mediawiki/core@master] RecentChange: Log entries of not-bots can be internally marked as such

Reason:

Change 742208 covers this already

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

The fix is ready, but requires another change, 742208, to be merged into mediawiki core.

Change 742208 had a related patch set uploaded (by Urbanecm; author: Matěj Suchánek):

[mediawiki/core@master] Allow marking recent changes about logged actions with bot flag

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

Change 742208 merged by jenkins-bot:

[mediawiki/core@master] Allow marking recent changes about logged actions with bot flag

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

The fix is ready, but requires another change, 742208, to be merged into mediawiki core.

Thanks for providing the fix here! I've reviewed your patch and merged the core change. I think your patch should also remove the current treatment (which is broken), ie. call to addTemporaryUserRights from ReassignMentees::doReassignMentees. Once that's done, I'll be happy to merge the GrowthExperiments patch as well.

Change 897186 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Bulk mentor reassignment won't spam RecentChanges

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

Msz2001 claimed this task.

The part of the task related to RecentChanges has been fixed. Whom to send the notifications should be decided on in T298070 (if ever becomes active again).

Moving to QA instead. Thanks for the fix!

Etonkovidova subscribed.

Checked in enwiki wmf.27 and testwki wmf.1 - the fix works as expected:

  • Logs of growthexperiments should be hidden in RecentChanges by default (like bot edits)