Changes between Version 1 and Version 2 of TracTickets

Show
Ignore:
Timestamp:
10/09/08 04:57:21 (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTickets

    v1 v2  
    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'''.  
     
    1010An issue is assigned to a person who must resolve it or reassign the ticket to someone else. 
    1111All 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.  
    1412 
    1513== Ticket Fields == 
     
    2725 * '''Milestone''' - When this issue should be resolved at the latest. 
    2826 * '''Assigned to/Owner''' - Principal person responsible for handling the issue. 
    29  * '''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.'' 
    3028  
    3129 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. 
     
    3634'''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]. 
    3735 
     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] 
    3839 
    3940== Changing and Commenting Tickets == 
     
    5657'''Note:''' See TracNotification for how to configure email notifications of ticket changes. 
    5758 
    58 === State Diagram === 
    59 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw 
    60  
     59'''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 
    6160 
    6261== Default Values for Drop-Down Fields == 
     
    6463The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: 
    6564 
    66  * `default_type`: Default ticket type 
    6765 * `default_component`: Name of the component selected by default 
    68  * `default_version`: Name of the default version 
    6966 * `default_milestone`: Name of the default milestone 
    7067 * `default_priority`: Default priority value 
    7168 * `default_severity`: Default severity value 
     69 * `default_type`: Default ticket type 
     70 * `default_version`: Name of the default version 
    7271 
    7372If any of these options are omitted, the default value will either be the first in the list, or an empty value, depending on whether the field in question is required to be set. 
     
    8382== Assign-to as Drop-Down List == 
    8483 
    85 If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have logged in and set their email address to populate the drop-down field. 
     84If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have accessed the project to populate the drop-down field. 
    8685 
    87 ''Note that this feature is '''still experimental as of version 0.9'''. There is no way to only display a subset of all known users as possible ticket owners. Nor is there a convenient way to remove emeritus users short of directly modifying the database.'' 
    88  
     86To appear in the dropdown list, a user needs be registered with the project, ''i.e.'' a user session should exist in the database. Such an entry is automatically created in the database the first time the user submits a change in the project, for example when editing the user's details in the ''Settings'' page, or simply by authenticating if the user has a login. Also, the user must have `TICKET_MODIFY` [TracPermissions permissions]. 
    8987 
    9088== Preset Values for New Tickets == 
     
    9492Possible variables are : 
    9593 
     94 * '''type''' - The type droplist 
    9695 * '''reporter''' - Name or email of the reporter 
    9796 * '''summary''' - Summary line for the ticket 
     
    106105 * '''cc''' - The list of emails for notifying about the ticket change 
    107106 
    108 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 
     107'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]] 
    109108 
    110  
    111 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification 
     109---- 
     110See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery