Bug watches can't be removed

...I was just going to report this one! I managed to create *duplicate* watches to the same remote bug:

  https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-i810/+bug/28326

which it didn't pick up on either! :-)

This bug has been marked "In Progress" for two months; is work in fact in progress?

A fix for this bug was in progress, I even had a branch up for review, but then it was decided that the problem made this bug critical should be solved in another way. In the next rollout it will be possible to unlink bug watches and edit bugtasks manually in order to reject them.

We should still allow marking watches obsolete/dead or deleting them, because not doing so makes us unable to clean up old bugs.

Matthew, the suggested UI in the description doesn't work, since bug watches don't have to be associated to a specific bugtask. Could you add suggest an UI that works even for free-standing bug watches?

I could, but it would be nasty. Instead, I suggest first requiring bug watches to be associated with a specific bugtask, *then* fixing this bug. :-)

On Wed, Oct 18, 2006 at 08:00:13AM -0000, Matthew Paul Thomas wrote:
> I could, but it would be nasty. Instead, I suggest first requiring bug
> watches to be associated with a specific bugtask, *then* fixing this
> bug. :-)

I agree with this in principle, but it requires that every distribution and
product be registered in Launchpad first, and that is not very practical for
us.

--
 - mdz

On Wed, Oct 18, 2006 at 08:19:17AM -0000, Matt Zimmerman wrote:
> On Wed, Oct 18, 2006 at 08:00:13AM -0000, Matthew Paul Thomas wrote:
> > I could, but it would be nasty. Instead, I suggest first requiring bug
> > watches to be associated with a specific bugtask, *then* fixing this
> > bug. :-)
>
> I agree with this in principle, but it requires that every distribution and
> product be registered in Launchpad first, and that is not very practical for
> us.

Matt (mdz) has a good point here. I think it's better first to fix this
bug, then think about how we can require bug watches to be associated
with a specific bugtask. I don't think the bug watch edit page is
visited that frequently, I'm sure we can get away with doing something
nasty there :)

Having the possibility to delete bug watches is better than not to have
it at all, even if the UI isn't ideal. Matthew, if you don't propose any
better solution, I might just add a "Delete this bug watch" button to
the bug watch edit page ;)

I'll add a delete button to the bug watch edit page.

A fix is in the review queue.

Fixed in RF 4412.

just curious, what is "RF 4412"? a commit number?

On Wed, Jan 17, 2007 at 05:42:04PM -0000, Sebastien Bacher wrote:
> just curious, what is "RF 4412"? a commit number?

It's a revision number on Launchpad mainline.

--
 - mdz

On Wed, Jan 17, 2007 at 05:42:04PM -0000, Sebastien Bacher wrote:
> just curious, what is "RF 4412"? a commit number?

Yes. It's short for revision 4412 in RocketFuel, which is the main
development branch.

This is available on edge, but it doesn't work yet because of a permissions issue in the database.