Changes between Version 4 and Version 5 of TracTickets


Ignore:
Timestamp:
Aug 6, 2008, 11:51:29 AM (14 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTickets

    v4 v5  
    22[[TracGuideToc]]
    33
    4 The Trac issue database provides simple but effective tracking of issues and bugs within a project.
    5 
    6 '''Please use the [wiki:MaiaMailingLists mailing lists] to report and discuss problems with installation and configuration; Post tickets to report and track actual problems with the codebase.'''
     4The Trac ticket database provides simple but effective tracking of issues and bugs within a project.
    75
    86As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''.
     
    1210An issue is assigned to a person who must resolve it or reassign the ticket to someone else.
    1311All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
    14 
    15 '''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.
    1612
    1713== Ticket Fields ==
     
    2925 * '''Milestone''' - When this issue should be resolved at the latest.
    3026 * '''Assigned to/Owner''' - Principal person responsible for handling the issue.
    31  * '''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.''
    3228 
    3329 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
     
    3834'''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].
    3935
     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]
    4039
    4140== Changing and Commenting Tickets ==
     
    5857'''Note:''' See TracNotification for how to configure email notifications of ticket changes.
    5958
    60 === State Diagram ===
    61 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw
    62 
     59'''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
    6360
    6461== Default Values for Drop-Down Fields ==
     
    6663The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    6764
    68  * `default_type`: Default ticket type
    6965 * `default_component`: Name of the component selected by default
    70  * `default_version`: Name of the default version
    7166 * `default_milestone`: Name of the default milestone
    7267 * `default_priority`: Default priority value
    7368 * `default_severity`: Default severity value
     69 * `default_type`: Default ticket type
     70 * `default_version`: Name of the default version
    7471
    7572If 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.
     
    8582== Assign-to as Drop-Down List ==
    8683
    87 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.
    8885
    89 ''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.''
    90 
     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].
    9187
    9288== Preset Values for New Tickets ==
     
    9692Possible variables are :
    9793
     94 * '''type''' - The type droplist
    9895 * '''reporter''' - Name or email of the reporter
    9996 * '''summary''' - Summary line for the ticket
     
    108105 * '''cc''' - The list of emails for notifying about the ticket change
    109106
    110 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''
     107'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
    111108
    112 
    113 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
     109----
     110See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery