Proposed changes to workflow bug management

[Christian Robottom Reis]

> I still think it's useful to have this feature. I don't see why
> assigning a bug to a team as part of workflow is so difficult to
> understand as a concept.

Well, you have a use case which implies it's useful, but that view is at
odds with that assignment means in Launchpad -- and in fact, to most
people that look at such bugs.

It doesn't actually mean anything to assign a task to a team, in the
strict sense of assignment that Launchpad implies. There is nobody
responsible for it, and in fact, bugs can linger in the assigned state
before anybody has actually set it to Triaged (meaning it might not even
be a bug) and also well after that. Users get confused with the assignee
being set when in fact nobody is actually committed to fixing that bug.
It's unclear who to talk to to get information on progress.

I get the feeling that team assignment is used to produce a list of bugs
to work off from. I also think it's used mainly because of shortcomings
in the bug tags feature. If you tagged x86 bugs with an x86 tag and it
stuck, it would have the same effect of putting a bug on a list that
could then be looked at by a separate team -- all you'd need to do is
update bookmarks.
-- 
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125