Edgewall Software

Changes between Version 22 and Version 23 of NewTicket


Ignore:
Timestamp:
Aug 27, 2019, 1:38:53 AM (3 months ago)
Author:
Ryan J Ollos
Comment:

Make this page a bit more concise and DRY.

Legend:

Unmodified
Added
Removed
Modified
  • NewTicket

    v22 v23  
    1 = Important: Read This Before Creating a Ticket =
     1= Important: Read This Before Creating a Ticket
    22{{{
    33#!div class="important" style="border: double red; padding-left: 2em"
     
    55You are about to file a ticket against the Trac instance used to manage the **development of Trac**.
    66
    7 Note also that most of the plugins for Trac are not maintained here, but usually on TracHacks.
     7Note also that plugins for Trac are not maintained here, but usually on TracHacks.
    88
    99== This is not a demo or test system!
    1010If you'd like to see how Trac works, either [TracDownload download]
    11 and [TracInstall install] it locally (it's easy), or play with the [/demo-1.0] site.
     11and [TracInstall install] it locally (it's easy), or play with the [/demo-1.2] site.
    1212
    1313== This is not the place to ask for support and installation questions!
     
    2323}}}
    2424
    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 (only the administrator can deploy the fix it anyway).
     25== When to ''not'' create a ticket here
     26**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).
    2727
    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**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).
    2929
    3030Failing this, we'll close the ticket as invalid with the WrongTrac notice.
    3131
    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).
     32Finally, **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).
     33Likewise, //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).
    3434
    3535Failing this, we'll close the ticket as cantfix with the PluginIssue notice.
    3636
    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...
    38 Please take the time to search for an already existing ticket.
     37If 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...
     38Please take the time to search for an existing ticket.
    3939A good tip is to look for the verbatim text of the error you're seeing, e.g.
    4040{{{
     
    4646</form>
    4747}}}
    48 Alternatively, you can directly look at the list of open issues using a custom query, e.g. [query:type=defect&status!=closed&group=component all known defects, grouped by component].
     48Alternatively, 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].
    4949
    50 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.
     50The 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.
    5151
    52 == Yes, I think I've found a new bug ==
    53 
    54 Then please, by all means let us know!
    55 
     52== Yes, I think I've found a new bug
    5653If you haven't done it before, read the NewTicketGuidelines which will give you some tips about how to create a good bug report.
    5754Then proceed to [/newticket?type=defect create the bug report].
    5855
    59 If the issue has security implications, then you should send a mail to `security@edgewall.com` rather than create a ticket, so that we get a chance to fix the problem before it is disclosed to the world ;-)
     56If 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!
    6057
    6158Of course, improvement ideas (preferably with patches!) are also welcomed, and you can also [/newticket?type=enhancement create enhancement requests].
    6259
    63 If the issue is really a small glitch or a quick suggestion, and can be explained very concisely, then try the shortcut way and add it in the TracIdeas/ pages instead!
    64 
    65 And please, please, '''don't''' create test tickets (you have the [[span(title=demo for Trac 0.12,[/demo-0.12 demos])]] [[span(title=demo for Trac 1.0,[/demo-1.0 instances])]] for that), we prefer spending our time improving Trac rather than fighting spam. Thanks for your comprehension.
     60If 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.
    6661
    6762 -- The TracTeam