When linking a branch to a bug, please add an explanatory comment

Bug #392552 reported by Matt Zimmerman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

It's very cool that Launchpad links to the bug report when a bug is fixed in a
branch.  I wonder if it's possible for it to also annotate the bug report to
state that this happened, though.  It's not very clear when looking at the bug
report (particularly for a Launchpad outsider) what the message means: "Branch
linked: lp:apport"

I think it would be great if it also added a comment (like we do when a bug is
marked fixed in a package upload) which explains briefly what has happened,
e.g.: "<person> has committed a change to branch <branch> which they believe
fixes this bug.  <link to the diff> <bzr command for checking out the branch>
..."

I discussed this briefly with jml, and he recommended filing a wishlist bug
about it.

Matt Zimmerman (mdz)
Changed in launchpad:
importance: Undecided → Wishlist
affects: launchpad → launchpad-code
tags: added: bug-branch-links
Revision history for this message
Tim Penhey (thumper) wrote :

Do you envision a real comment being added or just a more descriptive activity?

I'm wondering how this would interact with private branches being added to public bug reports. Right now for those that can't see the branch, there is no indication (AFAIK), but by adding a comment we'd make that more visible.

I think this is just outgoing email right now. I'd be happy to make it more useful though :)

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 392552] Re: When linking a branch to a bug, please add an explanatory comment

On Tue, Jun 30, 2009 at 05:19:43AM -0000, Tim Penhey wrote:
> Do you envision a real comment being added or just a more descriptive
> activity?

I hadn't considered a more descriptive activity. I think that would
probably serve the same purpose. I assumed a comment because that's what
package uploads seem to do.

--
 - mdz

Jonathan Lange (jml)
Changed in launchpad-code:
importance: Wishlist → Low
status: New → Triaged
Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 392552] Re: When linking a branch to a bug, please add an explanatory comment

This may not be exactly the same bug, but: it would be nice if the
attachment of a bug appeared in the new unified timeline view of
changes and comments, because it would make the existence of the
branch more visible. There's another bug complaining that at the
moment it's a bit buried between the description and the first
comment.

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

Revision history for this message
Jonathan Lange (jml) wrote :

On Tue, Jul 7, 2009 at 7:40 PM, Martin Pool<email address hidden> wrote:
> This may not be exactly the same bug, but: it would be nice if the
> attachment of a bug appeared in the new unified timeline view of
> changes and comments, because it would make the existence of the
> branch more visible.

Doesn't it already?

jml

Revision history for this message
Martin Pool (mbp) wrote :

2009/7/8 Jonathan Lange <email address hidden>:
> On Tue, Jul 7, 2009 at 7:40 PM, Martin Pool<email address hidden> wrote:
>> This may not be exactly the same bug, but: it would be nice if the
>> attachment of a bug appeared in the new unified timeline view of
>> changes and comments, because it would make the existence of the
>> branch more visible.
>
> Doesn't it already?

It was a typo: I meant "attachment of a branch to a bug appeared in
the timeline", and no, that does not seem to happen at present. File
attachments do appear in the timeline.

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

Revision history for this message
Jonathan Lange (jml) wrote :

You're right :(

I distinctly remember Bjorn changing some bug-branch linking code to help support the linking appearing in the timeline view. I guess it never made it all the way to full-fledged feature.

I'll file a bug about it on malone.

Revision history for this message
Jonathan Lange (jml) wrote :
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.