Changes between Version 2 and Version 3 of TracTickets
- Timestamp:
- Mar 1, 2004, 7:13:29 PM (20 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v2 v3 5 5 As the central project management element of Trac, tickets are be used for '''bug reports''', '''feature requests'''. '''software support issues''' and '''project tasks'''. 6 6 7 As with the TracWiki, th esubsystem has been designed with the goal of making user contribution and participation as simple as possible. It should be easy to report bugs, ask questions and suggest improvements.7 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 easy to report bugs, ask questions and suggest improvements. 8 8 9 9 An issue is assigned a person who must resolve it or reassign the ticket to … … 17 17 * '''Reporter''' - The author of the ticket. 18 18 * '''Component''' - The project module or subsystem this ticket concerns. 19 * '''Version''' - The version of the project thatthis ticket pertains to.19 * '''Version''' - Version of the project does this ticket pertains to. 20 20 * '''Severity''' - What are the effects the issue described? Ranges from an ''enhancement'' request to ''blocker'' (must be fixed before next milestone). 21 21 * '''Priority''' - The importance of is the issue relative to other tasks. … … 28 28 * '''Summary''' - A brief description summarizing the problem or issue. 29 29 * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''. 30 31 == Changing and Commenting Tickets == 32 33 Once a ticket has been entered into Trac, you can at any time change the 34 information by '''annotating''' the bug. This means changes and comments to 35 the ticket are logged as a part of the ticket itsel. 36 37 When viewing a ticket, this log of changes will appear below the main ticket area. 38 39 ''In the Trac project, we use ticket comments to discuss issues and 40 tasks. This makes understanding the motivation behind a design- or implementation choice easier, when returning to it later.'' 41 42 '''Note:''' An important feature is being able to use TracLinks and 43 WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to 44 other issues, changesets or files to make your ticket more specific and easier 45 to understand. 46 47 See also: TracGuide, TracWiki