Changes between Version 1 and Version 2 of TracTickets


Ignore:
Timestamp:
Apr 13, 2011, 7:01:00 PM (13 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'''.
    … …  
    1111All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
    1212
    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.
    14 
    1513== Ticket Fields ==
    1614
    1715A  ticket contains the following information attributes:
    1816 
    19  * '''Reporter''' - The author of the ticket.
    20  * '''Type''' - The nature of the ticket (for example, defect or enhancement request)
     17 * '''Reporter''' — The author of the ticket.
     18 * '''Type''' — The nature of the ticket (for example, defect or enhancement request)
    2119
    22  * '''Component''' - The project module or subsystem this ticket concerns.
    23  * '''Version''' - Version of the project that this ticket pertains to.
    24  * '''Keywords''' - Keywords that a ticket is marked with.  Useful for searching and report generation.
     20 * '''Component''' — The project module or subsystem this ticket concerns.
     21 * '''Version''' — Version of the project that this ticket pertains to.
     22 * '''Keywords''' — Keywords that a ticket is marked with.  Useful for searching and report generation.
    2523
    26  * '''Priority''' - The importance of this issue, ranging from ''trivial'' to ''blocker''.
    27  * '''Milestone''' - When this issue should be resolved at the latest.
    28  * '''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.''
     24 * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''.
     25 * '''Milestone''' — When this issue should be resolved at the latest.
     26 * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
     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 
    31  * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    32  * '''Status''' - What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.
    33  * '''Summary''' - A brief description summarizing the problem or issue.
    34  * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point.
     29 * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
     30 * '''Status''' — What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.
     31 * '''Summary''' — A brief description summarizing the problem or issue.
     32 * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point.
    3533
    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 [trac:TicketTypes type], [trac:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or with the [trac:WebAdmin WebAdmin] plugin.
     37
     38'''Note:''' Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
    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
     71 * `default_owner`: Name of the default owner, ''if no owner for the component has been set''
    7272
    73 If 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.
     73If 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.  Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section (others in the "trac.ini" section).  The default owner for a ticket will be the component owner, if that is set, or `default_owner`, if not.
    7474
    7575
    … …  
    8383== Assign-to as Drop-Down List ==
    8484
    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.
     85If 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.
    8686
    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.''
     87To 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].
    8888
     89'''Note:''' See [http://pacopablo.com/wiki/pacopablo/blog/set-assign-to-drop-down Populating Assign To Drop Down] on how to add user entries at database level
     90
     91'''Note 2:''' If you need serious flexibility and aren't afraid of a little plugin coding of your own, see [http://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo] (disclosure: I'm the author)
     92
     93'''Note 3:''' Activating this option may cause some performance degradation, read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
    8994
    9095== Preset Values for New Tickets ==
    … …  
    9499Possible variables are :
    95100
    96  * '''reporter''' - Name or email of the reporter
    97  * '''summary''' - Summary line for the ticket
    98  * '''description''' - Long description of the ticket
    99  * '''component''' - The component droplist
    100  * '''version''' - The version droplist
    101  * '''severity''' - The severity droplist
    102  * '''keywords''' - The keywords
    103  * '''priority''' - The priority droplist
    104  * '''milestone''' - The milestone droplist
    105  * '''owner''' - The person responsible for the ticket
    106  * '''cc''' - The list of emails for notifying about the ticket change
     101 * '''type''' — The type droplist
     102 * '''reporter''' — Name or email of the reporter
     103 * '''summary''' — Summary line for the ticket
     104 * '''description''' — Long description of the ticket
     105 * '''component''' — The component droplist
     106 * '''version''' — The version droplist
     107 * '''severity''' — The severity droplist
     108 * '''keywords''' — The keywords
     109 * '''priority''' — The priority droplist
     110 * '''milestone''' — The milestone droplist
     111 * '''owner''' — The person responsible for the ticket
     112 * '''cc''' — The list of emails for notifying about the ticket change
    107113
    108 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''
     114'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
    109115
    110 
    111 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
     116----
     117See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery