| | 1 | = Ticket Types = |
| | 2 | |
| | 3 | ''Warning: this feature is not yet availble in the mainline Trac'' |
| | 4 | |
| | 5 | When creating a new ticket, Trac enables you to select |
| | 6 | the appropriate type for that ticket. |
| | 7 | Indeed, a ''ticket'' can represent anything ranging from |
| | 8 | a problem report, a support request, an idea for a new feature |
| | 9 | or actually any artifact that fits in your development process. |
| | 10 | |
| | 11 | Among issue trackers, Trac was initially on the ''undifferentiated'' camp, |
| | 12 | everything was treated the same and it was only from the description |
| | 13 | that one could tell in which category a ticket would fit. |
| | 14 | |
| | 15 | However, the need for a more structured partitioning of the ticket type |
| | 16 | appeared (e.g. #919, #1399) and several Trac sites where actually |
| | 17 | tweaking the ''severity'' field to be the ''ticket type'', or creating |
| | 18 | TracTicketsCustomFields for that purpose. |
| | 19 | |
| | 20 | Now, with the ticket ''type'' field, one store this information as |
| | 21 | part of the core properties of the ticket, which permits to display |
| | 22 | the type of a ticket in more interesting places, usually next to |
| | 23 | the ticket number: |
| | 24 | * in the Ticket page's title http://projects.edgewall.com/trac/attachment/wiki/TicketTypes/tt_title.png |
| | 25 | * in the TracTimeline http://projects.edgewall.com/trac/attachment/wiki/TicketTypes/tt_timeline.png |
| | 26 | Also, it's the first field you can select when creating a new ticket. http://projects.edgewall.com/trac/attachment/wiki/TicketTypes/tt_new.png |
| | 27 | |
