Launchpad itself

The newbug-style email a new bug contact receives on product/package reassignment is confusing

Bug #51046 reported by Brad Bollenbach
14
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Christian Reis

Bug Description

When a bug is reassigned to a new product or package, the new bug contacts get what looks like a newbug mail, e.g. it will say "Public [or private] bug reported" in the body, so that they get the full description of the bug.

This means that if someone reassigns a bug to a new product/package on which they're the bug contact, they'll get a newbug mail, which is confusing. We should tweak this email to ensure that it doesn't look like a newbug mail.

Tags: lp-bugs
Revision history for this message
Brad Bollenbach (bradb) wrote :

Mark suggested this email be formatted like:

You are now subscribed, or assigned, to the following bug:

[bug title]

[bug description goes here, all in a single paragraph.]

[bug url]

Christian Reis (kiko)
Changed in malone:
importance: Untriaged → High
status: Unconfirmed → Confirmed
Revision history for this message
Matt Zimmerman (mdz) wrote :

I suggested some time ago that when transferring a bug to a new person (specifically in the context of forwarding bugs upstream), the new person should get the entire conversation of the bug. Is this still planned?

Revision history for this message
Brad Bollenbach (bradb) wrote : Re: [Bug 51046] Re: The newbug-style email a new bug contact receives on product/package reassignment is confusing

On Wed, 2006-16-08 at 20:30 +0000, Matt Zimmerman wrote:
> I suggested some time ago that when transferring a bug to a new person
> (specifically in the context of forwarding bugs upstream), the new
> person should get the entire conversation of the bug. Is this still
> planned?

Sounds like a good idea. I'll think through this more when I/we get to
fixing this bug.

Christian Reis (kiko)
Changed in malone:
importance: High → Medium
Revision history for this message
Christian Reis (kiko) wrote :

I have a fix for this bug in my bug 3797 branch. However, it doesn't sent the entire conversation of the bug. We should file a separate bug if we want that feature (it's not hard but this branch doesn't need to be any bigger).

Changed in malone:
assignee: nobody → kiko
status: Confirmed → In Progress
Revision history for this message
Christian Reis (kiko) wrote :

Landed in RF 3982.

Changed in malone:
status: In Progress → Fix Committed
Christian Reis (kiko)
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.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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