Changes between Initial Version and Version 1 of TracTickets

Oct 11, 2005, 12:24:32 AM (17 years ago)



  • TracTickets

    v1 v1  
     1= The Trac Ticket System =
     4The Trac issue database provides simple but effective tracking of issues and bugs within a project.
     6As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''.
     8As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible. It should be as easy as possible to report bugs, ask questions and suggest improvements.
     10An issue is assigned to a person who must resolve it or reassign the ticket to someone else.
     11All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
     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.
     15== Ticket Fields ==
     17A  ticket contains the following information attributes:
     19 * '''Reporter''' - The author of the ticket.
     21 * '''Component''' - The project module or subsystem this ticket concerns.
     22 * '''Version''' - Version of the project that this ticket pertains to.
     23 * '''Severity''' - What are the effects the issue described? Ranges from an ''enhancement'' request to ''blocker'' (must be fixed before next milestone).
     24 * '''Keywords''' - Keywords that a ticket is marked with.  Useful for searching and report generation.
     26 * '''Priority''' - The importance of is the issue relative to other tasks.
     27 * '''Milestone''' - When this issue should be resolved at the latest.
     28 * '''Assigned to''' - Principal person responsible for handling the issue.
     29 * '''Cc''' - A list of other associated people. ''note: this does '''not''' imply responsiblity or any other policy.
     31 * '''Resolution''' - Reason for why a ticket was closed, such as {{{fixed}}}, {{{invalid}}}, {{{duplicate}}}, etc.
     32 * '''Status''' - What is the current status? (One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.)
     33 * '''Summary''' - A brief description summarizing the problem or issue.
     34 * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''.
     36== Changing and Commenting Tickets ==
     38Once a ticket has been entered into Trac, you can at any time change the
     39information by '''annotating''' the bug. This means changes and comments to
     40the ticket are logged as a part of the ticket itself.
     42When viewing a ticket, this log of changes will appear below the main ticket area.
     44''In the Trac project, we use ticket comments to discuss issues and
     45tasks. This makes understanding the motivation behind a design- or implementation choice easier, when returning to it later.''
     47'''Note:''' An important feature is being able to use TracLinks and
     48WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to
     49other issues, changesets or files to make your ticket more specific and easier
     50to understand.
     52'''Note:''' See TracNotification for how to configure email notifications of ticket changes.
     54=== State Diagram ===
     57== Advanced: Preset values for New Tickets from URL ==
     59To create a link to the new-ticket form filled with preset values, you need to call the /newticket? URL with variable=value separated by &.
     61Possible variables are :
     63 * '''reporter''' - Name or email of the reporter
     64 * '''summary''' - Summary line for the ticket
     65 * '''description''' - Long description of the ticket
     66 * '''component''' - The component droplist
     67 * '''version''' - The version droplist
     68 * '''severity''' - The severity droplist
     69 * '''keywords''' - The keywords
     70 * '''priority''' - The priority droplist
     71 * '''milestone''' - The milestone droplist
     72 * '''owner''' - The person responsible for the ticket
     73 * '''cc''' - The list of emails for notifying about the ticket change
     75'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''
     78See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification