| 2005-10-19 22:03:27 |
Sitsofe Wheeler |
bug |
|
|
added bug |
| 2005-11-23 22:13:25 |
Brad Bollenbach |
malone: status |
New |
Accepted |
|
| 2005-11-23 22:13:25 |
Brad Bollenbach |
malone: priority |
|
Low |
|
| 2005-11-23 22:13:25 |
Brad Bollenbach |
malone: statusexplanation |
|
A few people brought this up at UBZ in Montreal. Won't have time to get to it for a while, but it sounds like something that could be very useful. |
|
| 2005-11-23 22:13:25 |
Brad Bollenbach |
malone: assignee |
|
bradb |
|
| 2006-04-17 02:16:34 |
Matthew Paul Thomas |
description |
Sometimes it is nice to be prompted for what information to enter into a bug report (even if you are familiar with the bug reporting process). This way one knows that ALL the key information has been entered in a clear structure. It also encourages good bug reporting habits. Many Bugzillas (GNOME, Red Hat, Mozilla) have templates to help raise the quality of bug reports.
Ties in with bug #2574 . |
Sometimes it is nice to be prompted for what information to enter into a bug report (even if you are familiar with the bug reporting process). This way one knows that ALL the key information has been entered in a clear structure. It also encourages good bug reporting habits. Many Bugzillas (GNOME, Red Hat, Mozilla) have templates to help raise the quality of bug reports.
These prompts will need to be product/distribution/package/product-specific, edited by the relevant maintainer. On pages where Malone does not know the exact target ahead of time (for example, the package name on a distribution bug reporting page), the prompt will need to be pulled and inserted using JavaScript whenever the target is selected or changed.
See also bug #2574. |
|
| 2006-05-10 09:21:49 |
Matthew Paul Thomas |
description |
Sometimes it is nice to be prompted for what information to enter into a bug report (even if you are familiar with the bug reporting process). This way one knows that ALL the key information has been entered in a clear structure. It also encourages good bug reporting habits. Many Bugzillas (GNOME, Red Hat, Mozilla) have templates to help raise the quality of bug reports.
These prompts will need to be product/distribution/package/product-specific, edited by the relevant maintainer. On pages where Malone does not know the exact target ahead of time (for example, the package name on a distribution bug reporting page), the prompt will need to be pulled and inserted using JavaScript whenever the target is selected or changed.
See also bug #2574. |
Sometimes it is nice to be prompted for what information to enter into a bug report (even if you are familiar with the bug reporting process). This way one knows that ALL the key information has been entered in a clear structure. It also encourages good bug reporting habits. Many Bugzillas (GNOME, Red Hat, Mozilla) have templates to help raise the quality of bug reports.
See also bug #2574 and bug 43893. |
|
| 2006-05-10 13:37:40 |
Brad Bollenbach |
malone: assignee |
bradb |
|
|
| 2006-05-10 13:37:40 |
Brad Bollenbach |
malone: statusexplanation |
A few people brought this up at UBZ in Montreal. Won't have time to get to it for a while, but it sounds like something that could be very useful. |
|
|
| 2008-04-25 13:36:54 |
Przemek K. |
marked as duplicate |
|
43893 |
|
| 2008-04-25 14:25:15 |
William Grant |
removed duplicate marker |
43893 |
|
|
| 2009-02-05 22:02:09 |
Joey Stanford |
bug |
|
|
added subscriber OEM Services Team |
| 2011-04-26 23:06:58 |
Robert Collins |
summary |
Malone should support bug reporting templates |
Malone does not support bug reporting templates |
|
| 2011-04-26 23:07:00 |
Robert Collins |
launchpad: importance |
Medium |
Low |
|
| 2011-05-30 08:29:12 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
