Filing bugs with classifications other than packages
Often, a user filing a bug does not know to which package their bug belongs. However, seeking to be helpful, they often attempt to provide some context anyway, and the only channel available to them is the Package field. This results in many bug reports being incorrectly filed against packages whose names contain 'wireless', 'installer', 'upgrade', etc.
Instead, we should allow them to provide this information in a non-disruptive way, and use it to route bugs to the correct team for package-level classification. Types of bugs which could be handled this way include:
- Installation bugs
- Upgrade bugs
- Kernel bugs
- Printing bugs
- Desktop bugs
and other cases where there is a team with clear responsibility for an area of functionality which doesn't correspond to a particular package.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by