|Version 6 (modified by 14 years ago) ( diff ),|
Important: Read This Before Creating a Ticket
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 (he's the only one able to fix it anyway).
Also, if you have an issue with some other software (Pidgin, MacPorts, etc.) 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).
Finally, if the problem concerns a Trac plugin , there is no point in creating a ticket on this site either. You should 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 if 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… Please take the time to search for an already existing ticket. A good tip is to look for the verbatim text of the error you're seeing, e.g.
Alternatively, you can directly look at the list of open issues using a custom query, e.g. known issues for 0.11dev grouped by component.
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!
Of course, improvement ideas (preferably with patches!) are also welcomed, and you can also 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