The Trac Ticket System

Table of Contents

Trac问题数据库提供了简单但有效的地在一个项目内对问题和错误的跟踪。

作为Trac的一个中心的项目管理元素，tickets被应用于问题报告、特性请求、软件支持问题和项目任务。

如同 TracWiki 一样，这个子系统的设计目标就是：使用户贡献和分享尽可能的简单。应该尽可能地简单来报告错误、问问题和建议改进。

一个问题被指派给一个人，他必须解决经或重新指派这个ticket给其他人。所有的tickets可以在任何时修被修改、加注、指派、设定优先级和进行讨论。

注意:为了充分使用这个ticket系统，把它用作一个in bucket，用在你的项目中搜集相和处理任务，而不要只是用于问题/错误的报告。

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

一个ticket包含下面的信息属性一：

  • Reporter - ticket的报告人
  • Component - 这个ticket所涉及到的项目模块或子系统
  • Version - 这个ticket所指定的项目的版本
  • Severity - 问题描述的严重程度。范围从enhancement(增强)请求到blocker(阻塞)(必须在下一个里程碑前被修正)
  • Priority - 这个问题相对于其它问题的重要程度（优先级）
  • Milestone - 最迟到何时这个问题应该被解决
  • Resolution - 为什么一个ticket被关闭的原因，如fixed(修正)、invalid(无效)、duplicate(重复)，等等
  • Keywords - 一个ticket被标记的关键字。用于搜索或生成报告
  • Assigned to - 处理此问题的主要负责人
  • Cc - 相关人员的列有。注意：这并不意味着责任或其它策略
  • Status - 当前的状态
  • Summary - 问题的简短说明
  • Description - ticket的主体。一个好的描述应该是明确的、描述性的点到要害的

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

一旦一个ticket已经被输入进Trac，你可以在任何时候通过评注错误来修改信息。这就意味着对于ticket的修改和评论被作为ticket本身的一部分被记录进日志。

当查看一个ticket时，这个修改日志将显示在主ticket区的下面。

在Trac项目中，我们使用ticket评论来讨论问题和任务。这样使得当回到以前去理解一个设计或实现的选择背后的活动容易一些。

注意：一个重要的特性就是：可以在ticket的描述和评论中使用 TracLinks 和 WikiFormatting 。使用 TracLinks 来引用其它的问题、修改集或文件，可以使你的ticket更明确和容易理解。

Note: 查阅 TracNotification 来了解如何为ticket的修改配置email通知功能。

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

http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw

Advanced: Preset values for New Tickets from URL

你可以使用 /newticket? 的URL的形式来生成新的ticket。链接后面带有预设的变量值，使用 variable=value 的形式，中间用 & 分隔。

可能的变量：

  • reporter - 报告的人名字或email
  • summary - ticket的简单说明
  • description - ticket的长描述
  • component - 涉及到的模块
  • version - 涉及到的版本
  • severity - 严重程度
  • keywords - 关键字
  • priority - 优先级
  • milestone - 里程碑
  • owner - ticket的响应者
  • cc - 通知ticket变化的email列表

示例: /trac/newticket?summary=Compile%20Error&version=1.0&component=gui

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 &.

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