Launchpad itself

Link bug to revision

Asked by Steven Sheehy

Hi,

Is it possible to link a bug to a changeset/revision? I know it is possible to link a bug to a branch, but I'm wondering if you can also link it to a bazaar (or vcs import) changeset?

If it's not possible, I would like to request such a feature. I don't want to have to create an entire branch just to fix every minor bug, but I still want to know which code fixed that bug when viewing the bug report. For example, say a project has bug #1234 and commits a fix in their trunk. Say this commit is revision 40. Then bug #1234 should give a link to revision 40 and bug #1234 should show up on the branch's recent revision entry for revision 40.

Thanks,
Steven

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Steven Sheehy (steven-sheehy) said : 		#2

I don't think an answer should expire because no one answered it...

Revision history for this message
Christian Reis (kiko) said : 		#3

This feature doesn't exist yet. I think it's probably worth thinking of it from the commit side -- if a bug is referred to in a commit log for the trunk branch for that project, then maybe we could mark the bug as fix committed. Tim?

Revision history for this message
Tim Penhey (thumper) said : 		#4

It is certainly an interesting proposition. The main problem is working out how to do record this information in the UI.

We certainly know which revision of a bazaar branch fixes a bug if the user uses the "--fixes lp:1324" type revision property upon committing, and showing this in the UI is possible, but one question is where?

Another issue is how would we allow this to be linked for an import branch? We'd want some way to indicate that the bug was fixed in a particular revision of the imported branch.

One deficiency we have right now is that our current data model doesn't really support this clearly, and we need to improve it.

Revision history for this message
Christian Reis (kiko) said : 		#5

On Wed, Mar 12, 2008 at 04:47:46AM -0000, Tim Penhey wrote:
> We certainly know which revision of a bazaar branch fixes a bug if the
> user uses the "--fixes lp:1324" type revision property upon committing,
> and showing this in the UI is possible, but one question is where?

Maybe include a bug icon close to the revision display?

> Another issue is how would we allow this to be linked for an import
> branch? We'd want some way to indicate that the bug was fixed in a
> particular revision of the imported branch.

You could offer UI to link it directly. But to me that's almost a
separate problem -- displaying the metadata that is already associated
with a Bazaar branch seems like a more direct win.
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

Can you help with this problem?

Provide an answer of your own, or ask Steven Sheehy for more information if necessary.

To post a message you must log in.