Changes between Version 2 and Version 3 of TracTickets


Ignore:
Timestamp:
11/18/04 18:03:00 (19 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTickets

    v2 v3  
    11= The Trac Ticket System =
     2[[TracGuideToc]]
    23
    3 The Trac issue database provides simple but effective tracking of issues and bugs within the project.
     4The Trac issue database provides simple but effective tracking of issues and bugs within a project.
    45
    56As the central project management element of Trac, tickets are used for '''bug reports''',  '''feature requests''', '''software support issues''' and '''project tasks'''.
    67
    7 As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible. It should be easy to report bugs, ask questions and suggest improvements.
     8As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible. It should be as easy as possible to report bugs, ask questions and suggest improvements.
    89
    9 An issue is assigned to a person who must resolve it or reassign the ticket to
    10 someone else. All tickets can be edited, annotated, assigned, prioritized and
    11 discussed at any time.
     10An issue is assigned to a person who must resolve it or reassign the ticket to someone else.
     11All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
     12
     13'''Note:''' To make full use of the ticket system, use it as an ''in bucket'' for ideas and tasks for your project, rather than just bug/fault reporting.
    1214
    1315== Ticket Fields ==
    … …  
    2426 * '''Keywords''' - Keywords that a ticket is marked with.  Useful for searching and report generation.
    2527 * '''Assigned to''' - Principal person responsible for handling the issue.
    26  * '''Cc''' - A list of other associated people. ''note: this does '''not''' imply responsiblity or any other policy.
    27 
     28 * '''Cc''' - A list of other associated people. ''Note: this does '''not''' imply responsibility or any other policy.
    2829 * '''Status''' - What is the current status?
    29 
    3030 * '''Summary''' - A brief description summarizing the problem or issue.
    3131 * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''.
    … …  
    4747to understand.
    4848
    49 See also:  TracGuide, TracWiki
     49'''Note:''' See TracNotification for how to configure email notifications of ticket changes.
     50
     51=== State Diagram ===
     52http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw
     53
     54== Advanced: Preset values for New Tickets from URL ==
     55
     56To create a link to the new-icket form filled with preset values, you need to call the /newticket? URL with variable=value separated by &.
     57
     58Possible variables are :
     59
     60 * '''reporter''' - Name or email of the reporter
     61 * '''summary''' - Summary line for the ticket
     62 * '''description''' - Long description of the ticket
     63 * '''component''' - The component droplist
     64 * '''version''' - The version droplist
     65 * '''severity''' - The severity droplist
     66 * '''keywords''' - The keywords
     67 * '''priority''' - The priority droplist
     68 * '''milestone''' - The milestone droplist
     69 * '''owner''' - The responsable of the ticket
     70 * '''cc''' - The list of email for notify the ticket change
     71
     72'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''
     73
     74
     75See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification