Allow specifying the notification level for structural subscriptions
Bug #213261 reported by
Björn Tillenius
This bug report is a duplicate of:
Bug #672507: Add bug_notification_level to the structural +subscribe view.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
In Progress
|
Low
|
Graham Binns | ||
Bug Description
When subscribing to bugs for a project, milestone, etc., it should be possible to indicate how much information you want. For example, only status changes or status changes and comments.
| Changed in malone: | |
| milestone: | none → 1.2.5 |
| Changed in malone: | |
| assignee: | Abel Deuring (adeuring) → nobody |
| status: | In Progress → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Henrik Nilsen Omma (henrik) wrote | #1 |
| tags: | added: story-better-bug-notification |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #2 |
| Changed in malone: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Graham Binns (gmb) |
Revision history for this message
| Deryck Hodge (deryck) wrote | #3 |
To post a comment you must log in.
This is causing us some pain at the moment.
Our (ISD team) users are generally not very technical and often don't realise what's happening when they get bugmail from LP. We would like to start using tags and states more actively to organise our bugs but are restricted by the bug mail that would send to our users.
It would be good to be able to specify the traffic level on a per-project basis. We would then turn off notifications for changes to states, importance, milestones and tags.