bzr commit with --fixes lp:xxxx has no impact on the status of the referenced bug

Bug #318439 reported by Lionel Dricot on 2009-01-18
64
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

I'm using launchpad + bzr for my project.

When I push a branch with some commit marked as "--fixes lp:xxx", the status of the bug is not changed.

I know that Launchpad understand it because it links the bzr branch to the bug. It simply doesn't modify the status of the bug.

Jonathan Lange (jml) wrote :

We'll mark the bug as "in progress" once there's a (not-merged, not-abandoned) branch that fixes the bug, and "fix committed" if that branch is trunk.

Changed in malone:
assignee: nobody → jml
importance: Undecided → High
status: New → Triaged
Jonathan Lange (jml) wrote :

I started working on this, but got blocked on the difficulty of writing tests for the scanner. Blocked on bug 333696. It'd be nice to fix bug 334099 before working on this too, but not necessary.

Jonathan Lange (jml) wrote :

Not going to get a chance for a while.

Changed in launchpad-bazaar:
assignee: jml → nobody
Thomas Mashos (tgm4883) wrote :

Seems it should also leave a comment on the bug that it is changing the status for, and in that comment it should reference which revision on the branch it was fixed in (perhaps a link to the code too)

If you are doing "bzr commit --fixes=lp:bug#", it should change the bug status, and it shouldn't change the status without leaving a comment (with the revision number)

summary: - bzr --fixes lp:xxxx doesn't change the status of the bug
+ bzr commit with --fixes lp:xxxx has no impact on the status of the
+ referenced bug
Robert Collins (lifeless) wrote :

Still nice to do but not a current priority. Patches gratefully considered!

Changed in launchpad:
importance: High → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers