Changes between Version 3 and Version 4 of TracTickets


Ignore:
Timestamp:
Dec 16, 2007, 9:52:54 PM (17 years ago)
Author:
trac
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • TracTickets

    v3 v4  
    22[[TracGuideToc]]
    33
    4 The Trac issue database provides simple but effective tracking of issues and bugs within a project.
     4The Trac ticket database provides simple but effective tracking of issues and bugs within a project.
    55
    66As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''.
    … …  
    2525 * '''Milestone''' - When this issue should be resolved at the latest.
    2626 * '''Assigned to/Owner''' - Principal person responsible for handling the issue.
    27  * '''Cc''' - A list of other associated people. ''Note that this does not imply responsiblity or any other policy.''
     27 * '''Cc''' - A comma-separated list of other users or E-Mail addresses to notify. ''Note that this does not imply responsiblity or any other policy.''
    2828 
    2929 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    30  * '''Status''' - What is the current status?  See TracWorkflow
     30 * '''Status''' - What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.
    3131 * '''Summary''' - A brief description summarizing the problem or issue.
    3232 * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point.
    … …  
    3434'''Note:''' Versions of Trac prior to 0.9 did not have the ''type'' field, but instead provided a ''severity'' field and different default values for the ''priority'' field. This change was done to simplify the ticket model by removing the somewhat blurry distinction between ''priority'' and ''severity''. However, the old model is still available if you prefer it: just add/modify the default values of the ''priority'' and ''severity'', and optionally hide the ''type'' field by removing all the possible values through [wiki:TracAdmin trac-admin].
    3535
    36 '''Note:''' the ''type'' (TicketTypes), ''component'' (TicketComponent), ''version'' (TicketVersion), ''priority'' (TicketPriority) and ''severity'' (TicketSeverity) fields can all be managed through [wiki:TracAdmin trac-admin].
     36'''Note:''' the [wiki:TicketTypes type], [wiki:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or with the WebAdmin plugin.
     37
     38'''Note:''' Description of the builtin ''priority'' values is available at [wiki:TicketTypes#Whyistheseverityfieldgone]
    3739
    3840== Changing and Commenting Tickets ==
    … …  
    5456
    5557'''Note:''' See TracNotification for how to configure email notifications of ticket changes.
     58
     59=== State Diagram ===
     60[[Image(http://trac.edgewall.org/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.png?format=raw)]]
     61
    5662
    5763== Default Values for Drop-Down Fields ==
    … …  
    101107 * '''cc''' - The list of emails for notifying about the ticket change
    102108
    103 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''
     109'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
    104110
    105111----
    106 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
     112See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery