Important: Read This Before Creating a Ticket

⚠️ Is this really the Trac instance you're looking for?

⚠️ This is not a demo or test system!

The demo site is here:demo-1.4

⚠️ This is not the place to ask for support and installation questions!

When tonot 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 ticketon their instance of Trac, not here (which is the Trac for Trac itself).

Failing this, we'll close the ticket as invalid with theWrongTrac notice.

Finally,if the problem concerns a Tracplugin, 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 rightcomponent for the plugin, or the plugin maintainer won't notice).Likewise,ideas for new plugins are best expressed as​"Request a Hack" tickets on that community site, or directly shared with a larger public on the TracMailingList (pick Trac-dev if you intend to contribute on the coding).

Failing this, we'll close the ticket as cantfix with thePluginIssue notice.

If you're a Trac administrator and you've found a bug in Trac, there's a good chanceyou'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.

Alternatively, you can review the list of open issues using a custom query, e.g.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 theNewTicketGuidelines which will give you some tips about how to create a good bug report.Then proceed tocreate the bug report.

If the issue has security implications, send an email tosecurity@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 alsocreate enhancement requests.

If the issue is a suggestion or idea, and can be explained very concisely, add it in theTracIdeas/ pages instead. TheMailingList is another good place to raise an idea for discussion, and you'll reach a larger audience of developers and contributors.

— TheTracTeam