#3812 closed enhancement (duplicate)
add note on how to create a bug report
Reported by: | wkornewald | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | wkornewald | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
In the ticket creation form, between the ticket "Type" and the "Full description" there should be a note which will help increase the bug report quality for big projects with less qualified users:
For bug reports please specify:
- how to reproduce
- experienced behavior
- expected behavior
Attachments (0)
Change History (5)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Indeed, for internal projects it's not necessary, but I think that any openly accessible bug tracker should have these instructions. People just don't know how to report bugs and we should tell them which information we need.
comment:3 by , 18 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
#2021 requested a template that could be included on the "New Ticket" page, which is implemented as "site_newticket.cs". While the usage of that include was different for #2021, I think it's a suitable solution for this ticket as well, so I'm closing this as a duplicate.
So, simply put the content you want in "templates/site_newticket.cs" under your Trac project.
comment:4 by , 18 years ago
Milestone: | 0.10.1 |
---|
comment:5 by , 18 years ago
I think that it would be better to have something like "site_newticket_description.cs", so the message is placed right before the description field instead of above the "your email or username" and "summary" fields.
I think this really depends on the project and/or the company policy.
You can edit the ticket template to add this kind of information, but I don't think this should be part of the mainstream release.