No way of deliberately requesting someones input in a bug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
In projects/packages with a high volume of bugs, it's impracticable to follow up every comment through a mailing list, so people usually assign the user they want input to the bug. That's pretty much abusing the tool, because:
- as it may imply that the "pinged" user is the one responsible for the discussion to continue, but that's not necessarily true, neither most of the cases; Also more than one person's input might be required.
- there are a lot of workarounds to filter bugs in launchpad, it would be good if we could tell bugs are being taken care of by checking if they're assigned to someone (like launchpad team does).
- we could change bug's description with something parseable, but that would be yet another addition to the description which will become unmanageable soon.
- <add your own reason here>
A button with "Request user's input" that shows a person picker and send him an email requesting input might work fine.
So I have some questions about this that make me not sure how to triage it.
Do people really still assign people to bugs as a means of requesting input? I thought we fixed the bug tracker so you can only assign yourself unless you're the bug supervisor.
Also, I assumed practice would be to subscribe someone and ask a question directly. Is this not the case? If it is, how is this breaking down due to large numbers of bugs. I know I get my mail differently when directly subscribed. But I do recognize that I don't get the same volume of mail as Ubuntu devs.
I'm not disputing this is an issue for Ubuntu devs. Just wondering if we really need to change Launchpad or if subscriptions are enough and a cultural/process shift is required.