Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Changes between Initial Version and Version 1 of TracTickets

10/01/05 16:01:31 (14 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 '''bug reports''',  '''feature requests''', '''software support issues''' and '''project tasks'''.  
     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. 
     20 * '''Component''' - The project module or subsystem this ticket concerns. 
     21 * '''Version''' - Version of the project that this ticket pertains to. 
     22 * '''Severity''' - What are the effects the issue described? Ranges from an ''enhancement'' request to ''blocker'' (must be fixed before next milestone). 
     23 * '''Priority''' - The importance of is the issue relative to other tasks. 
     24 * '''Milestone''' - When this issue should be resolved at the latest. 
     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? 
     30 * '''Summary''' - A brief description summarizing the problem or issue. 
     31 * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''. 
     33== Changing and Commenting Tickets == 
     35Once a ticket has been entered into Trac, you can at any time change the 
     36information by '''annotating''' the bug. This means changes and comments to 
     37the ticket are logged as a part of the ticket itself. 
     39When viewing a ticket, this log of changes will appear below the main ticket area. 
     41''In the Trac project, we use ticket comments to discuss issues and 
     42tasks. This makes understanding the motivation behind a design- or implementation choice easier, when returning to it later.'' 
     44'''Note:''' An important feature is being able to use TracLinks and 
     45WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to 
     46other issues, changesets or files to make your ticket more specific and easier 
     47to understand. 
     49'''Note:''' See TracNotification for how to configure email notifications of ticket changes. 
     51=== State Diagram === 
     54== Advanced: Preset values for New Tickets from URL == 
     56To create a link to the new-icket form filled with preset values, you need to call the /newticket? URL with variable=value separated by &.  
     58Possible variables are : 
     60 * '''reporter''' - Name or email of the reporter 
     61 * '''summary''' - Summary line for the ticket 
     62 * '''description''' - Long description of the ticket 
     63 * '''component''' - The component droplist 
     64 * '''version''' - The version droplist 
     65 * '''severity''' - The severity droplist 
     66 * '''keywords''' - The keywords  
     67 * '''priority''' - The priority droplist 
     68 * '''milestone''' - The milestone droplist 
     69 * '''owner''' - The responsable of the ticket 
     70 * '''cc''' - The list of email for notify the ticket change 
     72'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 
     75See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification