Changes between Version 57 and Version 58 of TracTickets
- Timestamp:
- Apr 27, 2011, 9:31:30 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v57 v58 20 20 21 21 * '''Reporter''' — The author of the ticket. 22 23 22 * '''Type''' — The nature of the ticket (for example, defect or enhancement request). See TicketTypes for more details. 24 25 23 * '''Component''' — The project module or subsystem this ticket concerns. 26 27 24 * '''Version''' — Version of the project that this ticket pertains to. 28 29 25 * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation. 30 31 26 * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities where defined. 32 33 * '''Milestone''' — When this issue should be resolved at the latest. A pull-down menu containing a role of milestones. 34 27 * '''Milestone''' — When this issue should be resolved at the latest. A pull-down menu containing a list of milestones. 35 28 * '''Assigned to/Owner''' — Principal person responsible for handling the issue. 36 37 29 * '''Cc''' — A comma-separated list of other users or E-Mail addresses to notify. ''Note that this does not imply responsiblity or any other policy.'' 38 39 30 * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. 40 41 31 * '''Status''' — What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}. 42 43 32 * '''Summary''' — A brief description summarizing the problem or issue. Simple text without WikiFormatting. 44 45 33 * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point. Accepts WikiFormatting. 46 34 … … 58 46 Then, annotations like changes and comments to the ticket are logged as a part of the ticket itself. When viewing a ticket, the history of changes will appear below the main ticket area. 59 47 60 Comment editing (available since 0.12) is meant to be used to make small corrections to comments, like fixing formatting, forgotten WikiFormatting or spelling errors, not major edits. For longer edits, you should be adding a new comment instead. 61 * Editing a comment will not produce a new entry on [/timeline] while entering a new comment or other changes will do. 48 Comment editing (available since 0.12) is meant to be used to make small corrections to comments, like fixing formatting, forgotten WikiFormatting or spelling errors, not major edits. For longer edits, you should be adding a new comment instead. Editing a comment will not produce a new entry on [/timeline] while entering a new comment or other changes will do. 62 49 63 * Anyway comments which where edited keep a track of changes, helping for traceability. 64 65 Updating the "last changed" time is useful to detect any modification to a ticket through an API, as explained in the description. 50 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket. This allows easily detecting changes to a ticket. 66 51 67 52