= Important: Read This Before Creating a Ticket =
{{{
#!div class=important style="border: double red"

You are about to file a ticket against Trac.

Please note that '''this is not a demo or test system'''.
Rather, it is used for the development of Trac itself. 
If you'd like to see how Trac works, either [TracDownload download] 
and [TracInstall install] it locally, or check the unofficial
[http://www.hosted-projects.com/trac/TracDemo/Demo demo site].

Support and installation questions should be asked on the
[MailingList mailing list] or [IrcChannel IRC channel],
not filed as tickets. 
Also, please [search:?ticket=on check] whether the issue 
you've encountered has been reported [MostFrequentDuplicates before].

For us to be able to help you and resolve your issue as fast as possible,
please check the [NewTicketGuidelines new ticket guidelines]
to make sure you're not leaving out some vital information.
}}}

== 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.
{{{
#!html
<form action="/search">
 <input type="text" size="60" name="q" value='"AssertionError: Authentication information not available."' />
 <input type="hidden" name="ticket" value="on" />
 <input type="submit" value="Search" />
</form>
}}}
Alternatively, you can directly look at the list of open issues using a custom query, e.g. [query:milestone=0.11|0.11.1&type=defect&status!=closed&group=component 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!

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].

If the issue has security implications, then you should send a mail to trac-security@googlegroups.com rather than create a ticket, so that we get a chance to fix the problem before it is disclosed to the world ;-)

Of course, improvement 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