Comment 11 for bug 5786
Revision history for this message
| Matthew Paul Thomas (mpt) wrote Re: NeedsInfo should be moved into a separate bug or bugtask flag | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
"Why should it be assigned to the designer?" Because that's who needs to work on it next.
"What if it were just a simple bit of design input required?" As Bjorn said, just ask them directly.
"How do I make sure that I don't lose track of ultimately being responsible for fixing the bug?" If you're really possessive about a bug, wanting nobody else to fix it, then (a) ask for it to be reassigned back to you once the preliminary work is done, or (b) keep it assigned to you and create a dependent bug assigned to the other person (using the Description to note the dependency until proper dependencies are implemented).
In summary, I think using Needs Info for anything other than "the bug is not yet described in an understandable and reproducible manner" is bogus. If what you really want is a way to say "this bug needs input from multiple people", then extend the assignee field to allow multiple values. But if a bug is blocked on input from one specific person, it should be assigned to that person.