Bugs should have the ability to verify the bug guidelines are followed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When looking at bugs a typical situation is that I need more information from a reporter. There is a pretty standard list of things I'd like, and usually the entire comment is me asking for one or more of them. It would be nice if Launchpad could help with that.
Currently what happens is that most packages have a wiki page that describes how to generate various information needed by maintainers. For example, here's the one for GNOME Power Manager:
https:/
As you can see, there is a large list of things that could be generated depending on the situation.
If we had that list in Launchpad there would be a couple benefits. The first would be that I coudl select the peices of information that I need, and have documentation and comments generated based on that. Also, when users upload that information they could check it off. I would love it if a bug couldn't be taken out of "Needs Information" by a user until those items are provided.
summary: |
- Bugs should have the ability to specify what information is needed + Bugs should have the ability to verify the bug guidelines are followed |
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: feature |
I don't think that this is a dup of that bug. That bug is about having instructions on reporting the bug. I'm asking for a check list of things that should be included when chaning the status to "Needs Info". For instance:
Stauts: [Needs Info]
Need: [x] Screenshot [info]
[ ] Log file [info]
[x] Config file [info]
This way the reporter knows specifically what is needed and the triager can specify exactly what is required in a more concise form. Also, then on upload there can be something to connect the two:
Attachment: [filename]
Description: My file
Resolves: [screenshot]