Changes between Version 3 and Version 4 of TracTickets
- Timestamp:
- Sep 27, 2006, 3:11:31 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v3 v4 10 10 An issue is assigned to a person who must resolve it or reassign the ticket to someone else. 11 11 All tickets can be edited, annotated, assigned, prioritized and discussed at any time. 12 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 12 15 13 == Ticket Fields == … … 36 34 '''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]. 37 35 36 '''Note:''' the ''type'' (TicketTypes), ''component'' (TicketComponent), ''version'' (TicketVersion), ''priority'' (TicketPriority) and ''severity'' (TicketSeverity) fields can all be managed through [wiki:TracAdmin trac-admin]. 38 37 39 38 == Changing and Commenting Tickets == … … 57 56 58 57 === State Diagram === 59 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw 58 [[Image(http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.png?format=raw)]] 60 59 61 60 … … 85 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. 86 85 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.'' 88 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]. 89 87 90 88 == Preset Values for New Tickets == … … 94 92 Possible variables are : 95 93 94 * '''type''' - The type droplist 96 95 * '''reporter''' - Name or email of the reporter 97 96 * '''summary''' - Summary line for the ticket … … 108 107 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 109 108 110 109 ---- 111 110 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
