| 25 | | * '''Resolution''' - Reason for why a ticket was closed, such as fixed, invalid, duplicate, etc. |
| 26 | | * '''Keywords''' - Keywords that a ticket is marked with. Useful for searching and report generation. |
| 27 | | * '''Assigned to''' - Principal person responsible for handling the issue. |
| 28 | | * '''Cc''' - A list of other associated people. ''Note: this does '''not''' imply responsibility or any other policy. |
| 29 | | * '''Status''' - What is the current status? |
| | 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.'' |
| | 28 | |
| | 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 | | * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''. |
| | 32 | * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point. |
| | 33 | |
| | 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]. |
| | 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]. |
| 56 | | To create a link to the new-icket form filled with preset values, you need to call the /newticket? URL with variable=value separated by &. |
| | 61 | == Default Values for Drop-Down Fields == |
| | 62 | |
| | 63 | The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: |
| | 64 | |
| | 65 | * `default_type`: Default ticket type |
| | 66 | * `default_component`: Name of the component selected by default |
| | 67 | * `default_version`: Name of the default version |
| | 68 | * `default_milestone`: Name of the default milestone |
| | 69 | * `default_priority`: Default priority value |
| | 70 | * `default_severity`: Default severity value |
| | 71 | |
| | 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. |
| | 73 | |
| | 74 | |
| | 75 | == Hiding Fields and Adding Custom Fields == |
| | 76 | |
| | 77 | Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through [wiki:TracAdmin trac-admin]. This of course only applies to drop-down fields, such as ''type'', ''priority'', ''severity'', ''component'', ''version'' and ''milestone''. |
| | 78 | |
| | 79 | Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information. |
| | 80 | |
| | 81 | |
| | 82 | == Assign-to as Drop-Down List == |
| | 83 | |
| | 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. |
| | 85 | |
| | 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]. |
| | 87 | |
| | 88 | == Preset Values for New Tickets == |
| | 89 | |
| | 90 | To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with variable=value separated by &. |
