OOPS via email interface when assigning a bug to a team with not contact address at the same time a new bugtask is created

Bug #126943 reported by Björn Tillenius
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Eleanor Berger

Bug Description

If you create a new task, and assign that task to a team that doesn't have a contact address, an unhandled exceptoin is raised when creating the bug notifications, since it tries to include the team's contact address (which is None).

This happens only when using the e-mail interface, since you can't do this in the web UI.

Changed in malone:
assignee: nobody → intellectronica
Revision history for this message
Eleanor Berger (intellectronica) wrote :

Do we have a link to an example OOPS? I'm having difficulties reproducing this using the test suite, so looking at the traceback will be very helpful.

Revision history for this message
Eleanor Berger (intellectronica) wrote :

Marking `Incomplete` until I can get more information on how to observe this bug.

Changed in malone:
status: New → Incomplete
Revision history for this message
Eleanor Berger (intellectronica) wrote :

I have now managed to reproduce and isolate the error, please ignore comment #2

Changed in malone:
status: Incomplete → Confirmed
Revision history for this message
Eleanor Berger (intellectronica) wrote :

Fixed and submitted for review

Changed in malone:
status: Confirmed → In Progress
Revision history for this message
Eleanor Berger (intellectronica) wrote :

RF rev. 4818

Changed in malone:
status: In Progress → Fix Committed
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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