2009/9/1 Matthew Paul Thomas <email address hidden>:
> I think the clearest way of fixing this would be to abolish bug watches
> not associated with a bugtask. If a bug watch is related to the bug, it
> should be linked to a project or package. If it's not, there's no point
> in it being there at all.
I'd actually like to go further than that and abolish the notion of
bug "watches" altogether. Bugs are all bugs; Launchpad's job is to
represent them all in the same way, whether their primary instance
resides in LP's DB or in someone's Bugzilla DB. Launchpad should
present bugs as either being "local" or "remote," but the
differentiation should be subtle so that users that don't have to care
don't, er, have to care.
2009/9/1 Matthew Paul Thomas <email address hidden>:
> I think the clearest way of fixing this would be to abolish bug watches
> not associated with a bugtask. If a bug watch is related to the bug, it
> should be linked to a project or package. If it's not, there's no point
> in it being there at all.
I'd actually like to go further than that and abolish the notion of
bug "watches" altogether. Bugs are all bugs; Launchpad's job is to
represent them all in the same way, whether their primary instance
resides in LP's DB or in someone's Bugzilla DB. Launchpad should
present bugs as either being "local" or "remote," but the
differentiation should be subtle so that users that don't have to care
don't, er, have to care.