Launchpad itself

Owner can't unsubscribe from project's bugs without setting bug supervisor

Bug #636918 reported by William Grant on 2010-09-13

This bug report is a duplicate of: Bug #113825: Null bug supervisor is confusing. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Triaged	Low	Unassigned

Bug Description

If a project has no bug supervisor set, the owner is notified of all bug changes. Unlike the bug supervisor, they have no option to unsubscribe.

A workaround is to set the bug supervisor to the owner, then remove the subscription.

The problematic bit is this:

    def getAlsoNotifiedSubscribers(self, recipients=None, level=None):
        [snip]
            # If the target's bug supervisor isn't set,
            # we add the owner as a subscriber.
            pillar = bugtask.pillar
            if pillar.bug_supervisor is None:
                also_notified_subscribers.add(pillar.owner)
                if recipients is not None:
                    recipients.addRegistrant(pillar.owner, pillar)

Tags:

Revision history for this message

Deryck Hodge (deryck) wrote on 2010-09-13:

A simple fix is to remove the also notified line here and either create a structural subscription when the project is created or make the owner the bug supervisor when the bug tracking is enabled. This doesn't fix existing projects, but would fix it going forward. The data could be updated after this patch lands.

These are, of course, just ideas off the top of my head. They may have downsides, and I'm completely open to other suggestions.

Thanks for the bug report, William.

Cheers,
deryck

Changed in malone:
status:	New → Triaged
importance:	Undecided → Medium
tags:	added: story-better-bug-notification

Revision history for this message

William Grant (wgrant) wrote on 2010-09-13:

Maybe the Bugs enabling workflow could warn if you don't set a bug supervisor, asking the owner if they want to subscribe?

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-09-28:

This is the same code that is spamming ~registry. That code is also not checking that the project uses Launchpad bugs. Consider that the upstream bug report uses the bug supervisor for a registered upstream project; users may be in that role for other reason then receive email.

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-09-28:

this looks like a duplicate of bug 579025 which was marked low.

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-10-14:

bug 579502 lists the same lines of code regarding registrants (the default owner) and the fact that there is not test if the project uses launchpad to track bugs.

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-11-18:

In few months all owners, drivers, bug supervisors, and security contacts will be granted access to project bugs regardless of subscription. That means subscriptions will only provide communication to users in project roles. We want to switch to subscription because it will provide levels of communication--the current approach is an unregulated torrent. I see two courses of action:

We announce we are dropping the automatic mailing to owners, the user can subscribe if he chooses
or we subscribe the owners, then make the announcement, where upon the user removes or changes the subscription.

Gary Poster (gary) on 2011-01-21

tags:

removed: story-better-bug-notification

Curtis Hovey (sinzui) on 2011-09-22