Initial merge proposal email should quote the description of any linked bugs

Bug #523256 reported by Matthew Revell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Since bug 390866 was fixed the initial merge proposal email links to any associated bug reports.

During the UDS-L user interviews, someone requested that the description of the bug be quoted in the email. He said that right now, he can't conduct a code review entirely through email because he has to go into the web interface in order to read the bug report.

Can we offer an option to have the description of any related bugs included in the initial merge proposal email?

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 523256] [NEW] Initial merge proposal email should quote the description of any linked bugs

On 18 February 2010 02:52, Matthew Revell <email address hidden> wrote:
> Public bug reported:
>
> Since bug 390866 was fixed the initial merge proposal email links to any
> associated bug reports.
>
> During the UDS-L user interviews, someone requested that the description
> of the bug be quoted in the email. He said that right now, he can't
> conduct a code review entirely through email because he has to go into
> the web interface in order to read the bug report.
>
> Can we offer an option to have the description of any related bugs
> included in the initial merge proposal email?

Yay, +1. urls would be good too.

--
Martin <http://launchpad.net/~mbp/>

Revision history for this message
Tim Penhey (thumper) wrote : Re: [Bug 523256] [NEW] Initial merge proposal email should quote the description of any linked bugs

On Thu, 18 Feb 2010 04:52:46 Matthew Revell wrote:
> Public bug reported:
>
> Since bug 390866 was fixed the initial merge proposal email links to any
> associated bug reports.
>
> During the UDS-L user interviews, someone requested that the description
> of the bug be quoted in the email. He said that right now, he can't
> conduct a code review entirely through email because he has to go into
> the web interface in order to read the bug report.
>
> Can we offer an option to have the description of any related bugs
> included in the initial merge proposal email?

  importance medium
  status incomplete
  tag code-review
  tag email

Instead of adding it to the body of the email, what about an attachment for
each bug with the bug description?

Changed in launchpad-code:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Launchpad itself because there has been no activity for 60 days.]

Changed in launchpad:
status: Incomplete → Expired
Revision history for this message
Martin Pool (mbp) wrote :

Attachments could work, but may cause difficulty with various mail clients not knowing what to do with the attachment. I suggest if we do this, we make it off by default and just put them inline when it's turned on.

Changed in launchpad:
importance: Medium → Low
status: Expired → Triaged
Revision history for this message
Martin Pool (mbp) wrote :

I've reopened this bug because it wasn't incomplete (so shouldn't expire) but I'm not sure if it even counts as Low.

My experience as a code review user is that the title of the bugs (which is now in the mp mail) gives me a reasonable clue what they are, but if that's not enough I probably want to skim the whole bug including all the comments. I don't think it makes sense to mail the whole bug page; if the person has all their mail offline they can probably find the bug within it.

Since this is Low it's not likely to get fixed soon so we can leave it and see if it gets any votes.

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.