Trac ticket templating to improve the quality of tickets

[johnbillion]

As I'm sure regular visitors to trac.wordpress.org will know, there are occasions when a ticket is submitted to Trac which is - albeit entirely unintentionally - not very helpful to anyone. An example might be:

hi i installed 2.1 and now my categories are broken, please fix it kthnxbye

Although the author of the ticket of course has the best of intentions, if they aren't familiar with any kind of software development then they may not be aware of what information the developers require in order to investigate and fix the problem.

I think it would be a great idea if a simple template for new tickets was implemented in WordPress Trac, just like in Google Code and Bugzilla. Here's a screen shot of Google Code's template: ​http://farm1.static.flickr.com/140/407267508_c096c0e52b_o.jpg

Its very basic and it won't stop anyone from just deleting the text and typing what they want, but it might help improve the quality of some of the bugs which are submitted.

Obviously the text will need to be more appropriate to WordPress. Any suggestions?

I think this is a good idea. I wonder what Trac has to offer (so we don't have to hack something in). Does Trac have plugins?

Trac does have plugins (​http://trac.edgewall.org/wiki/TracPlugins) but I haven't found one yet for ticket templating or anything similar.

I guess we write our own :D.

Any volunteers?

After doing some research ​http://trac.edgewall.org/wiki/TracTickets describes a method of seting default selections of fields. Description is a field that can have a default setting, probably to include the textr to make this ticket work.

So? Anyone want to implement this nice feature?

Thanks

+1. Sure, I'll try writing a template:

What steps should be taken to reproduce the problem?
1. 
2. 
3. 

What is the expected output? What did you see instead?


What version of WordPress are you using?


What web server are you using?


Are there any other environment variables that could be creating this bug?


Please provide additional information below.

see also: #9807