Changes between Version 2 and Version 3 of TracTickets

Mar 27, 2008, 7:31:47 AM (14 years ago)



  • TracTickets

    v2 v3  
    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.
    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.
    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.
    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.''
    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].
     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.
     38'''Note:''' Description of the builtin ''priority'' values is available at [wiki:TicketTypes#Whyistheseverityfieldgone]
    3940== Changing and Commenting Tickets ==
    5859=== State Diagram ===
    6465The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    66  * `default_type`: Default ticket type
    6767 * `default_component`: Name of the component selected by default
    68  * `default_version`: Name of the default version
    6968 * `default_milestone`: Name of the default milestone
    7069 * `default_priority`: Default priority value
    7170 * `default_severity`: Default severity value
     71 * `default_type`: Default ticket type
     72 * `default_version`: Name of the default version
    7374If 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.
    8586If 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.
    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.''
     88To 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. Also, the user must have `TICKET_MODIFY` [TracPermissions permissions].
    9090== Preset Values for New Tickets ==
    9494Possible variables are :
     96 * '''type''' - The type droplist
    9697 * '''reporter''' - Name or email of the reporter
    9798 * '''summary''' - Summary line for the ticket
    106107 * '''cc''' - The list of emails for notifying about the ticket change
    108 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''
     109'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
    111 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
     112See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery