Search to support answering every bug reported
Bug #6041 reported by
Steve Alexander
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Seb on the disto team has asked for a feature in Malone to show bugs on the distro (or its source packages) that have not had any comments added to them after the initial report.
This allows the distro team to ensure that every bug gets some kind of a response, even if they are too busy to move the bug to a CONFIRMED status.
An extra step would be to look for comments from someone responsible for that bug, such as its maintainers or the distro or motu teams. I'm not sure exactly how such a "who is responsible in some way" team is calculated, though.
| Changed in malone: | |
| assignee: | nobody → bradb |
| Changed in malone: | |
| status: | New → Accepted |
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #1 |
Revision history for this message
| Diogo Matsubara (matsubara) wrote | #2 |
| Changed in malone: | |
| assignee: | bradb → nobody |
| status: | Confirmed → Needs Info |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
To post a comment you must log in.
A bug that is perfectly described shouldn't need any comments, except for the purpose of making the reporter feel appreciated and noticed. Having Malone print "Sebastien Bacher confirmed this bug in Ubuntu Dapper" or "Daniel Holbach reassigned this bug in Ubuntu Dapper to Oliver Grawert" <https:/
If developers have time to look at a bug report but not mark it as Confirmed, that's a design problem in Malone. If developers have time to *comment* on a bug report but not to mark it as Confirmed, that's an even worse design problem.