Make WordPress Core

Opened 17 years ago

Closed 15 years ago

Last modified 15 years ago

#3897 closed task (blessed) (fixed)

Trac ticket templating to improve the quality of tickets

Reported by: johnbillion's profile johnbillion Owned by: lloydbudd's profile lloydbudd
Milestone: Priority: normal
Severity: normal Version:
Component: Site Keywords: trac
Focuses: Cc:


As I'm sure regular visitors to 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:

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?

Change History (15)

#1 @foolswisdom
17 years ago

  • Owner changed from matt to foolswisdom

#2 @rob1n
17 years ago

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?

#3 @johnbillion
17 years ago

Trac does have plugins ( but I haven't found one yet for ticket templating or anything similar.

#4 @rob1n
17 years ago

  • Severity changed from minor to normal

I guess we write our own :D.

Any volunteers?

#5 @Nazgul
17 years ago

  • Milestone set to 2.4 (future)

#6 @thee17
17 years ago

After doing some research 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.

#7 @darkdragon
17 years ago

  • Keywords hunt-sendnext added

So? Anyone want to implement this nice feature?

#8 @lloydbudd
17 years ago

  • Milestone changed from 2.4 to 2.5
  • Owner changed from foolswisdom to lloydbudd

#9 @santosj
17 years ago

  • Keywords hunt-sendnext removed


#10 @hansengel
17 years ago

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

What steps should be taken to reproduce the problem?

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.

#11 @Denis-de-Bernardy
15 years ago

  • Milestone changed from 2.9 to Unassigned

#12 @Denis-de-Bernardy
15 years ago

  • Type changed from enhancement to task (blessed)

#14 @Denis-de-Bernardy
15 years ago

  • Resolution set to fixed
  • Status changed from new to closed

#15 @Denis-de-Bernardy
15 years ago

  • Milestone Unassigned deleted
Note: See TracTickets for help on using tickets.