implicit (e.g.structural) subscriptions to private bugs don't work even when the subscriber has visibility on the bug

Bug #376186 reported by Brian Murray
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Apport
Won't Fix
Undecided
Unassigned
Launchpad itself
Fix Released
Low
Steve Kowalik

Bug Description

When apport files crash reports the ubuntu-crashes-universe team is automatically subscribed to these bug reports. (u-c-u has its mail go to a blackhole rather than permitting members to be notified via it). However subscribers of the package's bugs who are members of u-c-u (direct or indirect) are not subscribed to the bug report. Subsequently, they only start receiving e-mail about the bug when bug becomes public.

I think that if someone is subscribed to a package's bugs and a member of a team which can see the private bug they should also be directly subscribed to ensure they get e-mail notification of the private bug reports as this can be more important.

Related branches

Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 376186] [NEW] private bug implicit subscription

On Wed, May 13, 2009 at 08:02:00PM -0000, Brian Murray wrote:
> Public bug reported:
>
> When apport files crash reports the ubuntu-crashes-universe team is
> automatically subscribed to these bug reports however subscribers of the
> package's bugs who are members of u-c-u (direct or indirect) are not
> subscribed to the bug report. Subsequently, they only start receiving
> e-mail about the bug when bug becomes public.
>
> I think that if someone is subscribed to a package's bugs and a member
> of a team which can see the private bug they should also be directly
> subscribed to ensure they get e-mail notification of the private bug
> reports as this can be more important.

One option is to make ubuntu-crashes-universe have a mailing list, and
have everyone subscribe to that, doing filtering client-side.

If that isn't enough, I think we'd have to export the necessary API
methods (getting package subscribers and team memberships) if they
aren't already exported, and have apport subscribe the extra people.
It's not feasible doing this all in Launchpad, since we'd have to
change how things work currently and encode a policy that I wouldn't
really want to put in there.

    affects apport

Revision history for this message
Martin Pitt (pitti) wrote : Re: private bug implicit subscription

I'm not even sure we want that. When we designed the crash database, one of the explicit requests of many people was to not get spammed with all the crash reports.

Revision history for this message
Alexander Sack (asac) wrote :

> I think that if someone is subscribed to a package's bugs and a member of a team which can see the private
> bug they should also be directly subscribed to ensure they get e-mail notification of the private bug reports as
> this can be more important.

I agree with what martin suggests here. The idea of having a mailing list for all crashes does not work for me as it - as martin points out - would be far too much mail to cope for anyone.

Only problem that comes up with directly subscribing them is that lots of us filter directly subscribed bugs to a higher-prio mailbox. So imo launchpad should send private mails to all "Also notified" users if they can see the bug content (not sure if thats what martin suggested).

Curtis Hovey (sinzui)
tags: added: privacy
Changed in malone:
importance: Undecided → Low
status: New → Triaged
Graham Binns (gmb)
tags: added: story-better-bug-notification
Revision history for this message
Curtis Hovey (sinzui) wrote :

This scenario may be solvable with the suggested DSP admin who has full access to everything associated with it. We will also projects and distros to grant full view to users and teams so that subscription is not needed to access a bug.

tags: added: disclosure
Revision history for this message
Martin Pitt (pitti) wrote :

Closing apport task. While we are using LP bugs, the current system has worked well enough, we don't want to introduce a new bug spam mail source, and eventually there will be a proper crash database.

Changed in apport:
status: New → Won't Fix
summary: - private bug implicit subscription
+ structural subscriptions to private bugs don't work even when the
+ subscriber has visibility on the bug
description: updated
summary: - structural subscriptions to private bugs don't work even when the
- subscriber has visibility on the bug
+ implicit (e.g.structural) subscriptions to private bugs don't work even
+ when the subscriber has visibility on the bug
Curtis Hovey (sinzui)
tags: added: sharing
Revision history for this message
William Grant (wgrant) wrote :

Fixing this will probably also fix bug #901548, which is about assignees not being notified.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
assignee: nobody → Steve Kowalik (stevenk)
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Steve Kowalik (stevenk)
tags: added: bad-commit-15645 qa-bad
removed: qa-needstesting
Steve Kowalik (stevenk)
Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-bad
Changed in launchpad:
status: In Progress → Fix Committed
Steve Kowalik (stevenk)
tags: added: qa-ok
removed: qa-needstesting
Ian Booth (wallyworld)
Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in launchpad:
status: Fix Released → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.