Bug:+subscribe can't cope with existing BugSubscriptions with a bug_notification_level of NOTHING

Bug #721400 reported by Graham Binns on 2011-02-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Graham Binns

Bug Description

What happens:
Using the API, set a bug subscription's bug_notification_level to NOTHING. If you then browse to that bug's +subscribe page you'll get an OOPS, because Bug:+subscribe's validation doens't allow NOTHING as a bug_notification_level value. This also breaks the advanced subscription overlay. NB: This only currently affects the malone-alpha team.

What should happen:
The page (and overlay) should display fine. The validation code should allow for a bug_notifcation_level value of NOTHING in the DB but shouldn't allow it to be set using the UI.

See also bug 721410 and bug 721411.

Related branches

Gary Poster (gary) wrote :

As an alternate solution that may be simpler, Graham and I talked about a BugMute table that has records of person, bug to only keep track of what is muted. That seems cleaner than the enumeration.

description: updated
Graham Binns (gmb) on 2011-03-02
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Graham Binns (gmb)
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.03
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant) on 2011-03-06
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant) on 2011-03-07
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers