Changes between Version 3 and Version 4 of NewTicket

Timestamp:

Mar 11, 2008, 10:15:35 AM (16 years ago)

Author:

Christian Boos

Comment:

Now, it's still allowed to create tickets…

NewTicket

@@ -23 +23 @@
 
 == When to ''not'' create a ticket here ==
-Due to some ambiguous spelling on old error pages, Trac users were directed to create a ticket on this site whenever an internal error occurred in the Trac site they're using. '''If you're not the administrator of the Trac site''', please don't create a ticket here but rather inform your Trac administrator about the problem.
+Due to some ambiguous spelling on old error pages, Trac users were directed to create a ticket on this site whenever an internal error occurred in the Trac site they're using. '''If you're not the administrator of the Trac site''', please don't create a ticket here but rather inform your Trac administrator about the problem (he's the only one able to fix it anyway).
 
-Also, '''if you have an issue with other some software''' (Pidgin, MacPorts) for which the development is managed using Trac, be careful to create a ticket ''on their instance of Trac'', not here (which is the Trac for Trac itself).
+Also, '''if you have an issue with other some software''' (Pidgin, MacPorts, etc.) for which the development is managed using Trac, be careful to create a ticket ''on their own instance of Trac'', not here (which is the Trac for Trac itself).
 
-Finally, '''if the problem concerns a Trac plugin''', there is no point creating a ticket on this site either. You should rather report it to the plugins maintainer (for example, at http://trac-hacks.org if the plugin is hosted there - don't forget to specify the right ''component'' for the plugin, or the plugin maintainer won't notice).
+Finally, '''if the problem concerns a Trac ''plugin'' ''', there is no point in creating a ticket on this site either. You should rather report it to the plugin's maintainer (for example, on http://trac-hacks.org if the plugin is hosted there - in this case, don't forget to specify the right ''component'' for the plugin, or the plugin maintainer won't notice).
 
 Now you're a Trac administrator, you've found a genuine bug in Trac, then there's a good chance '''you're not the first person''' to notice it...
@@ -43 +43 @@
 
 The advantage of finding a pre-existing ticket is that there's often an existing workaround, or a patch waiting for feedback. In this case, please take the next step and participate at the bug fixing.
+
+== Yes, I think I've found a new bug ==
+
+Then please, by all means let us know!
+
+If you haven't done it before, read the NewTicketGuidelines which will give you some tips about how to create a good bug report.
+Then proceed to [/newticket?type=defect create the bug report].
+
+Of course, improvements ideas (preferably with patches!) are also welcomed, and you can also [/newticket?type=enhancement create enhancement requests].
+
+And please, please, '''don't''' create test tickets, we prefer spending our time improving Trac rather than fighting spam. Thanks for your comprehension.
+
+ -- The TracTeam