Changes between Version 1 and Version 2 of TracTickets


Ignore:
Timestamp:
04/22/2011 04:33:41 PM (4 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'''.  
     
    1515A  ticket contains the following information attributes: 
    1616  
    17  * '''Reporter''' - The author of the ticket. 
    18  * '''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) 
    1919 
    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. 
     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. 
    2323 
    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 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.'' 
    2828  
    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. 
     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. 
    3333 
    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 [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] 
    3739 
    3840== Changing and Commenting Tickets == 
     
    5557'''Note:''' See TracNotification for how to configure email notifications of ticket changes. 
    5658 
    57 === State Diagram === 
    58 [[Image(http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.png?format=raw)]] 
    59  
     59'''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 
    6060 
    6161== Default Values for Drop-Down Fields == 
     
    6969 * `default_type`: Default ticket type 
    7070 * `default_version`: Name of the default version 
     71 * `default_owner`: Name of the default owner, ''if no owner for the component has been set'' 
    7172 
    72 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. 
    7374 
    7475 
     
    8283== Assign-to as Drop-Down List == 
    8384 
    84 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. 
    8586 
    86 To 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]. 
     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]. 
     88 
     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. 
    8794 
    8895== Preset Values for New Tickets == 
     
    9299Possible variables are : 
    93100 
    94  * '''type''' - The type droplist 
    95  * '''reporter''' - Name or email of the reporter 
    96  * '''summary''' - Summary line for the ticket 
    97  * '''description''' - Long description of the ticket 
    98  * '''component''' - The component droplist 
    99  * '''version''' - The version droplist 
    100  * '''severity''' - The severity droplist 
    101  * '''keywords''' - The keywords  
    102  * '''priority''' - The priority droplist 
    103  * '''milestone''' - The milestone droplist 
    104  * '''owner''' - The person responsible for the ticket 
    105  * '''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 
    106113 
    107 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 
     114'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]] 
    108115 
    109116---- 
    110 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification 
     117See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery 
© 2003 – 2012 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy