Diff for "LEP/BetterBugSubscriptionsAndNotifications"

Not logged in - Log In / Register

Differences between revisions 24 and 25
Revision 24 as of 2010-06-02 13:13:51
Size: 7223
Editor: gmb
Comment:
Revision 25 as of 2010-11-25 12:20:35
Size: 7390
Editor: jml
Comment:
Deletions are marked like this. Additions are marked like this.
Line 136: Line 136:
'''Bugs are at:''' [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=story-better-bug-notification|story-better-bug-notification tag]]
Line 156: Line 158:
 * Bugs for this story are being tracked using the [[https://bugs.edge.launchpad.net/malone/+bugs?field.tag=story-better-bug-notification|story-better-bug-notification tag]].  * Bugs for this story are being tracked using the [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=story-better-bug-notification|story-better-bug-notification tag]].

Bug Notifications and Subscriptions: Less Noise, More Control

We should make subscribing to bugs something people want to do, not dread.

As an Ubuntu developer
I want control over my Launchpad subscriptions
so that I can get less noise and higher quality notices from Launchpad.

As an upstream developer
I want control over what information I get from Launchpad
so that I can easily find bugs related to my software.

There are two parts to this story -- less noise and more control.

So:

  • don't tell me about little things
  • don't tell me about my own actions (bug 548)

  • do provide individual control over the kinds of notifications

Rationale

Why now?

This story was taken up after consultation with Brian Murray, representing Ubuntu Platform QA. Launchpad's current focus is Getting Bugs Off Ubuntu. As a feature slot came open for development, we asked Brian what would help Ubuntu best manage the amount of bugs they have. He said, better bug subscribing and notifications.

Brian says, "people subscribe mostly to packages, but still get too much mail"

Stats from DB confirm packages are the most subscribed to: https://pastebin.canonical.com/29229/

What value does this bring?

Fixing bug notifications to be less noisy and bug subscribing to allow finer grained controls will allow people to manage the high volume of bugs against packages. This brings value to both Ubuntu and upstream developers by allowing people to better find bugs that interest them.

Stakeholders

Who will care about this work?

In particular, Ubuntu developers who are subscribed to large numbers of packages. In general, anyone who receives a lot of bug mail.

  • bdmurray
  • bryce
  • leanne
  • cjwatson
  • pitti
  • seb128
  • ubuntu server team
  • ubuntu kernel team
  • keybuk (Note: too much bug mail became a serious problem to the end of 10.04 LTS)
  • Elliot Murphy (or someone on his team)

When did we last talk to these stakeholders?

Only bdmurray has been consulted so far, and only in preparation for this story.

Constraints

This Feature Provides

  • Subscribe to HIGH or CRITICAL bugs for a package, project, distribution, etc.
  • Subscribe to a tag (bug 151129)

  • Subscribe to search results (related to bug 49752)

    -- The first two are special cases of the third. -mpt

  • Only subscribe to certain notices, e.g.
    • "tell me about change in status, importance, or comments, but not linked branches"
    • "tell me only about bug creation and transitions TO or FROM a final status"
    • These should be available for both bugs and structural subscriptions

This Features Does Not Provide

I don't think this feature should allow unlimited configuration for notifications. By that, I mean, you could select to be informed of importance changes, but not certain notice changes, i.e. you would not be able to say "tell me when this bug changes from UNDECIDED" or "from WISHLIST to HIGH" or some other very specific choice.

We would have a couple of often demanded statuses pre-configured, i.e. HIGH and CRITICAL for structural subscriptions.

Note from kfogel: we might want to reconsider unlimited configuration. If we can get the UI right, this would be very powerful, because it would enable many different kinds of stakeholders to satisfy their needs. The notification requirements of Ubuntu packagers might be very different from those of, say, hardware manufacturers.

  • jml agrees

  • deryck, who wrote the original not-unlimited-options proposal, agrees that we should make the subscription system as flexible as possible. As I understand from our design conversations, this is the plan. The original intent of my comment saying we should limit options was to say, let's be opinionated about what options are available in a "subscribe me" widget. We have to make choices there, obviously, and if we offer too many options to cover every possible use case, the widget becomes too complex to be useful for quickly subscribing to individual bugs or project/package bugs. I assumed subscribing to search results would cover the group who wants specific, perhaps uncommon, notifications.

    • Ahh, ok. That makes sense -- jml

Workflows

Bug page

New subscription:

  • A user clicks "Subscribe"
  • An overlay appears with the various options
  • The user makes choices, clicks "subscribe" on the overlay
  • The user is subscribed to the bug with those options

Existing subscriptions:

  • A user clicks "Edit Subscription"
  • An overlay appears with the various options
  • The user changes the choices and clicks "Update subscription"
  • The changes take effect

Packages, Projects

New subscription:

  • A user clicks "Subscribe"
  • An new page is loaded with the various options
  • The user makes choices, clicks "subscribe" on the form
  • The user is subscribed to the bug with those options and redirected back to the bugs homepage for the object

Existing subscriptions:

  • A user clicks "Edit Subscription"
  • An new page is loaded with the various options
  • The user changes the choices and clicks "Update subscription"
  • The changes take effect and the user is redirected to the bugs homepage for the object

Distributions

  • Structural subscriptions would be disallowed except for a team (to allow mailing list subscriptions to all bug notices)

Mockups will be added during the design phase.

Success

How will we know when we are done?

Bugs are at: story-better-bug-notification tag

How will we measure how well we have done?

Possibilities:

Useful info to have:

  • what filters/options are selected?

Notes

  • There are at least two axes here. One is "bugs I get told about" and the other is "actions on a bug that I get told about".
  • Bugs for this story are being tracked using the story-better-bug-notification tag.

LEP/BetterBugSubscriptionsAndNotifications (last edited 2011-03-21 12:55:00 by danilo)