NeedsInfo is currently a bugtask "status". This is problematic because it prevents us from representing:
* An unconfirmed bug that needs info (e.g. from the reporter)
* A confirmed bug that needs info (e.g. from the UI designer on how best to fix a UI issue)
IOW, it prevents us from maintaining the "state" of the bug while it's blocked on needing info from someone.
The propose solutions here include:
1. Making NeedsInfo a separate flag on the bug (...or bugtask?)
2. Using a text entry field that allows you to specify the name of the person from which the info is needed.
NeedsInfo is currently a bugtask "status". This is problematic because it prevents us from representing:
* An unconfirmed bug that needs info (e.g. from the reporter)
* A confirmed bug that needs info (e.g. from the UI designer on how best to fix a UI issue)
IOW, it prevents us from maintaining the "state" of the bug while it's blocked on needing info from someone.
The propose solutions here include:
1. Making NeedsInfo a separate flag on the bug (...or bugtask?)
2. Using a text entry field that allows you to specify the name of the person from which the info is needed.