Strict Standards: Redefining already defined constructor for class wpdb in /home/bdmurray/murraytwins.com/blog/wp-includes/wp-db.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /home/bdmurray/murraytwins.com/blog/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/bdmurray/murraytwins.com/blog/wp-includes/cache.php on line 389

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 556

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /home/bdmurray/murraytwins.com/blog/wp-includes/classes.php on line 678

Deprecated: Assigning the return value of new by reference is deprecated in /home/bdmurray/murraytwins.com/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/bdmurray/murraytwins.com/blog/wp-includes/theme.php on line 508
Brian’s Blog » Launchpad bug mail changes
Launchpad and Ubuntu24 Jun 2010 05:20 pm

As a part of my rotation with the Launchpad bugs team I am currently working on a Launchpad Enhancement Proprosal dealing with improved bug notifications and subscriptions. As a part of this work I thought I’d work on an easy bug about modifying the string in a new bug message to say “You have been assigned” instead of “You have been subscribed”. This ended up being more complicated than I had initially thought because there are actually multiple issues in that report and I had to learn the email notification system. But this makes the fix that much more rewarding.

So now when you are assigned a bug report you will receive an email with following in the body.

You have been assigned a bug task for a public bug by Brian Murray (brian-murray):

Its more than just s/subscribed/assigned/ because the assigner is actually identified - something that was not done before. Another fix made was preventing the assignee transition email notification from going to the assignee. You previously would get 2 emails when assigned, if you were not a bug subscriber, a notification about the new to you bug report and the assignment transition.

After fixing that bug I went ahead and fixed a bug that was bothering me in 2007! I wanted, and still want, to be able to filter on bug reports that I’ve reported which isn’t possible since I’m just listed as a subscriber. This particular bug really was easy (3 lines of code, 2 lines of comments and 7 lines of test) and now you can filter on an “X-Launchpad-Reporter:” header.

Okay not really now. Due to the way email notifications are sent you won’t actually be able to see these changes until they land on the production server next week.

4 Responses to “Launchpad bug mail changes”

  1. on 24 Jun 2010 at 10:02 pm Mackenzie

    Thank you thank you thank you!!!

  2. on 25 Jun 2010 at 2:21 am Ara

    Thanks for implementing this! I am really looking forward to these changes. Your experience in dealing with huge amount of bug mail is going to be a great addition to LP.

  3. on 26 Jun 2010 at 5:11 pm Brian Murray

    @Mackenzie - You are welcome, welcome, welcome! Is there something you particularly wanted?

  4. on 09 Jul 2010 at 6:47 pm Mackenzie

    I’d been wanting the reporter header for a while, so I’m happy to see it implemented :)

Feed on comments to this Post

Leave a Reply