= Important: Read This Before Creating a Ticket {{{ #!div class="important" style="border: double red; padding-left: 2em" == Is this really the Trac instance you're looking for? You are about to file a ticket against the Trac instance used to manage the **development of Trac**. Note also that plugins for Trac are not maintained here, but usually on TracHacks. == This is not a demo or test system! If you'd like to see how Trac works, either [TracDownload download] and [TracInstall install] it locally (it's easy), or play with the [/demo-1.2] site. == This is not the place to ask for support and installation questions! Use the [MailingList mailing list] or [IrcChannel IRC channel], you'll reach a bigger number of people likely to help you. Before reporting a bug, 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 **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 (only the administrator can deploy the fix anyway). **If you have an issue with some other software** (Pidgin, MacPorts, VirtualBox, 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). Failing this, we'll close the ticket as invalid with the WrongTrac notice. Finally, **if the problem concerns a Trac ''plugin''**, there is no point in creating a ticket on this site. You should report it to the plugin's maintainer, for example, on https://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). Likewise, //ideas for new plugins// are best expressed as [https://trac-hacks.org/newticket?component=Request-a-Hack '"Request a Hack"'] tickets on that community site, or directly shared with a larger public on the Trac MailingList (pick Trac-dev if you intend to contribute on the coding). Failing this, we'll close the ticket as cantfix with the PluginIssue notice. If you're a Trac administrator and you've found a bug in Trac, there's a good chance **you're not the first person** to notice it... Please take the time to search for an existing ticket. A good tip is to look for the verbatim text of the error you're seeing, e.g. {{{ #!html
}}} Alternatively, you can review the list of open issues using a custom query, e.g. [query:type=defect&status!=closed&group=component all known defects, grouped by component]. The advantage of finding an existing ticket is that there's often already a workaround, or a patch waiting for feedback. In this case, please take the next step and participate in the discussion and testing. == Yes, I think I've found a new bug 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, send an email to `security@edgewall.com` rather than creating 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]. If the issue is a suggestion or idea, and can be explained very concisely, add it in the TracIdeas/ pages instead. The MailingList is another good place to raise an idea for discussion, and you'll reach a larger audience of developers and contributors. -- The TracTeam