Changes between Version 30 and Version 31 of TracTickets
- Timestamp:
- Aug 28, 2006, 4:50:23 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v30 v31 11 11 All tickets can be edited, annotated, assigned, prioritized and discussed at any time. 12 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 15 13 == Ticket Fields == 16 14 … … 21 19 22 20 * '''Component''' - The project module or subsystem this ticket concerns. 23 * '''Version''' - Version of the project that this ticket pertains to. The integration between Trac and version control systems is explained in [TracAndVersioning]21 * '''Version''' - Version of the project that this ticket pertains to. 24 22 * '''Keywords''' - Keywords that a ticket is marked with. Useful for searching and report generation. 25 23 … … 57 55 58 56 === State Diagram === 59 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.png?format=raw 57 [[Image(http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.png?format=raw)]] 60 58 61 59 … … 85 83 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 84 87 ''Note that this feature is '''still experimental as of version 0.9''':'' 88 * 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. 89 * To appear in the dropdown list, a user should be registered in the project and trac should know user's email address, ''i.e.'' a user session should exist in the DB.[[BR]] 90 Such an entry is automatically created in the DB the first time the user submits a change in the project, for example on: 91 * edition of the user's details in the ''Settings'' page 92 * creation or update a wiki page 93 * creation or comment on a ticket 85 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]. 94 86 95 87 == Preset Values for New Tickets == … … 114 106 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 115 107 116 108 ---- 117 109 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
