Changes between Version 3 and Version 4 of TracTickets
- Timestamp:
- Apr 4, 2012, 2:28:20 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v3 v4 15 15 A ticket contains the following information attributes: 16 16 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) 19 19 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. 23 23 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.''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.'' 28 28 29 * '''Resolution''' —Reason for why a ticket was closed. One of {{{29 * '''Resolution''' - Reason for why a ticket was closed. One of {{{ 30 30 fixed 31 31 }}}, {{{ … … 38 38 worksforme 39 39 }}}. 40 * '''Status''' —What is the current status? One of {{{40 * '''Status''' - What is the current status? One of {{{ 41 41 new 42 42 }}}, {{{ … … 47 47 reopened 48 48 }}}. 49 * '''Summary''' —A brief description summarizing the problem or issue.50 * '''Description''' —The body of the ticket. A good description should be specific, descriptive and to the point.49 * '''Summary''' - A brief description summarizing the problem or issue. 50 * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point. 51 51 52 52 '''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]. … … 81 81 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: 82 82 83 84 85 83 86 * `default_component`: Name of the component selected by default 84 87 * `default_milestone`: Name of the default milestone … … 87 90 * `default_type`: Default ticket type 88 91 * `default_version`: Name of the default version 89 * `default_owner`: Name of the default owner, ''if no owner for the component has been set''90 92 91 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. 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.93 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. 92 94 93 95 … … 109 111 '''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) 110 112 111 '''Note 3:''' Activating this option may cause some performance degradation, read more about this in the [trac:TracPerformance#Configuration Trac performance] page.112 113 113 == Preset Values for New Tickets == 114 114 … … 117 117 Possible variables are : 118 118 119 * '''type''' —The type droplist120 * '''reporter''' —Name or email of the reporter121 * '''summary''' —Summary line for the ticket122 * '''description''' —Long description of the ticket123 * '''component''' —The component droplist124 * '''version''' —The version droplist125 * '''severity''' —The severity droplist126 * '''keywords''' —The keywords127 * '''priority''' —The priority droplist128 * '''milestone''' —The milestone droplist129 * '''owner''' —The person responsible for the ticket130 * '''cc''' —The list of emails for notifying about the ticket change119 * '''type''' - The type droplist 120 * '''reporter''' - Name or email of the reporter 121 * '''summary''' - Summary line for the ticket 122 * '''description''' - Long description of the ticket 123 * '''component''' - The component droplist 124 * '''version''' - The version droplist 125 * '''severity''' - The severity droplist 126 * '''keywords''' - The keywords 127 * '''priority''' - The priority droplist 128 * '''milestone''' - The milestone droplist 129 * '''owner''' - The person responsible for the ticket 130 * '''cc''' - The list of emails for notifying about the ticket change 131 131 132 132 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
