| Version 3 (modified by anonymous, 7 years ago) (diff) |
|---|
The Trac Ticket System
Table of Contents
The Trac issue database provides simple but effective tracking of issues and bugs within a project.
As the central project management element of Trac, tickets are used for bug reports, feature requests, software support issues and project tasks.
As 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.
An issue is assigned to a person who must resolve it or reassign the ticket to someone else. All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
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.
Ticket Fields
A ticket contains the following information attributes:
- Reporter - The author of the ticket.
- Component - The project module or subsystem this ticket concerns.
- Version - Version of the project that this ticket pertains to.
- Severity - What are the effects the issue described? Ranges from an enhancement request to blocker (must be fixed before next milestone).
- Priority - The importance of is the issue relative to other tasks.
- Milestone - When this issue should be resolved at the latest.
- Resolution - Reason for why a ticket was closed, such as fixed, invalid, duplicate, etc.
- Keywords - Keywords that a ticket is marked with. Useful for searching and report generation.
- Assigned to - Principal person responsible for handling the issue.
- Cc - A list of other associated people. Note: this does not imply responsibility or any other policy.
- Status - What is the current status?
- Summary - A brief description summarizing the problem or issue.
- Description - The body of the ticket. A good description should be specific, descriptive and to the point.
Changing and Commenting Tickets
Once a ticket has been entered into Trac, you can at any time change the information by annotating the bug. This means changes and comments to the ticket are logged as a part of the ticket itself.
When viewing a ticket, this log of changes will appear below the main ticket area.
In the Trac project, we use ticket comments to discuss issues and tasks. This makes understanding the motivation behind a design- or implementation choice easier, when returning to it later.
Note: An important feature is being able to use TracLinks and WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to other issues, changesets or files to make your ticket more specific and easier to understand.
Note: See TracNotification for how to configure email notifications of ticket changes.
State Diagram
Advanced: Preset values for New Tickets from URL
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 &.
Possible variables are :
- reporter - Name or email of the reporter
- summary - Summary line for the ticket
- description - Long description of the ticket
- component - The component droplist
- version - The version droplist
- severity - The severity droplist
- keywords - The keywords
- priority - The priority droplist
- milestone - The milestone droplist
- owner - The responsable of the ticket
- cc - The list of email for notify the ticket change
Example: /trac/newticket?summary=Compile%20Error&version=1.0&component=gui
See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
