Changes between Version 17 and Version 18 of NewTicket
- Timestamp:
- Jun 11, 2011, 10:48:18 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NewTicket
v17 v18 24 24 25 25 == When to ''not'' create a ticket here == 26 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).26 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). 27 27 28 Also, '''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).28 Also, **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). 29 29 30 30 Failing this, we'll close the ticket as invalid with the WrongTrac notice. 31 31 32 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). 32 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). 33 Likewise, //ideas for new plugins// are best expressed as [http://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). 33 34 34 35 Failing this, we'll close the ticket as cantfix with the PluginIssue notice. 35 36 36 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...37 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... 37 38 Please take the time to search for an already existing ticket. 38 39 A good tip is to look for the verbatim text of the error you're seeing, e.g.
