Link bug to revision

[Steven Sheehy]

This was previously opened as a question, but it has since been marked as answered so I thought I'd open a bug to track this feature request. I'd like to be able to link a bug to a changeset/revision. 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.

[Jonathan Lange (jml)]

You can already link bugs to revisions in Bazaar itself by doing:
    bzr commit --fixes lp:1234

However, there should be a way to link bugs to revisions in the web UI, and information about bug-revision links should be presented in the UI.

[Mikkel Kamstrup Erlandsen (kamstrup)]

It tightly knit teams where many revisions and branches are going back and forth it would be incredibly useful to be able to link to particular revisions in an inline style like we can with bugs, Fx lp:zeitgeist:1164 or lp:zeitgeist#1164. I tihnk I want to do this at least once per bug thread we have in the Zeitgeist project...

[Matt Giuca (mgiuca)]

Aside from whether or not you can link a bug to a revision in the web UI, there seems also to be no way to access that information later. On the bug's page, it will tell you which branch it was linked to, but not which revision. Is the rev-id even linked to the bug, or just the branch?

It looks like if you go to the branch view (in loggerhead) and navigate to the particular revision which --fixes the bug, there is a link to the bug ID, but from the bug ID, there is no link to the revision. So I would imagine that the data model for revisions in Bazaar includes metadata about which bug is linked to that revision, but the data model for bugs includes no metadata on which revision is linked to that bug.

Therefore, the first step for this bug is possibly adding data to the bug about which revision it was fixed in. (Unless I am mistaken, and that information is already in the bug, just not shown.)

[Johan Engelen (johanengelen)]

It is sad to see the importance being downgraded... Right now, I do not see the point of adding '--fixes lp:1234' to a commit. "On the bug's page, it will tell you which branch it was linked to, but not which revision." I do not understand why this bug-linking-feature was created in the first place, if the bug page itself would not link to the bug fix commit.

This feature request seems really simple to "fix", please do so! Thanks a bunch!

[Adam Candy (asc)]

+1, related to lp:131279, this would be helpful in the case of developing large projects where there are many project branches, associated merge requests, bugs and fixes - it would be useful to cross-reference these.