Bug Subscription Use Cases

[Matt Zimmerman]

On Wed, Aug 23, 2006 at 05:37:04PM -0400, Brad Bollenbach wrote:
> Hey all,
> 
> While working on fixing the "Also notified" subscription bug:
> 
>     https://launchpad.net/bugs/48860
> 
> I've been thinking more deeply about the faults in our current
> subscription UI. I wanted to check some of our assumptions:
> 
> 1. Do you guys ever need to subscribe teams to bugs, specifically a team
> that isn't otherwise assigned to the bug, and that isn't a bug contact
> on the affected software? If so, can you give examples of when this is
> useful?

Yes.  A classic example is subsystem teams, for example ubuntu-printing,
which cover printing-related issues in a variety of packages (including
packages whose primary purpose isn't printing, and so they aren't a bug
contact on them).

> 2. Do you ever have a compelling urge to unsubscribe from a bug on which
> you are a bug contact or assignee?

Assignee, no.  Bug contact, yes.

> 3. Going in a different direction, would it be useful to be able to
> subscribe or unsubscribe /anyone/ from a bug, or would that likely do
> more harm than good? (Consider, for example, that private bugs are
> visible only to subscribers.)

It would be useful to me as the sort of person who knows who ought to be
subscribed to a particular bug and can fix it up, but it doesn't really
bother me not having that capability so far.

> 4. If bug A is a dupe of bug B, and you were subscribed to A, you'll get
> subscribed to bug B "indirectly", automatically (happens already). Is
> there ever a reason that you'd want to unsubscribe from B, but remain
> subscribed to the dupe, A?

I can't think of any.

-- 
 - mdz