Changes between Version 1 and Version 2 of TracTickets


Ignore:
Timestamp:
09/16/05 00:03:52 (20 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTickets

    v1 v2  
    44The Trac issue database provides simple but effective tracking of issues and bugs within a project.
    55
    6 As the central project management element of Trac, tickets are used for '''bug reports''',  '''feature requests''', '''software support issues''' and '''project tasks'''.
     6As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''.
    77
    88As 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.
    … …  
    1818 
    1919 * '''Reporter''' - The author of the ticket.
     20
    2021 * '''Component''' - The project module or subsystem this ticket concerns.
    2122 * '''Version''' - Version of the project that this ticket pertains to.
    2223 * '''Severity''' - What are the effects the issue described? Ranges from an ''enhancement'' request to ''blocker'' (must be fixed before next milestone).
     24 * '''Keywords''' - Keywords that a ticket is marked with.  Useful for searching and report generation.
     25
    2326 * '''Priority''' - The importance of is the issue relative to other tasks.
    2427 * '''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.
    2728 * '''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?
     29 * '''Cc''' - A list of other associated people. ''note: this does '''not''' imply responsiblity or any other policy.
     30 
     31 * '''Resolution''' - Reason for why a ticket was closed, such as {{{fixed}}}, {{{invalid}}}, {{{duplicate}}}, etc.
     32 * '''Status''' - What is the current status? (One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.)
    3033 * '''Summary''' - A brief description summarizing the problem or issue.
    3134 * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''.
    … …  
    5457== Advanced: Preset values for New Tickets from URL ==
    5558
    56 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 &.
     59To create a link to the new-ticket form filled with preset values, you need to call the /newticket? URL with variable=value separated by &.
    5760
    5861Possible variables are :
    … …  
    6770 * '''priority''' - The priority droplist
    6871 * '''milestone''' - The milestone droplist
    69  * '''owner''' - The responsable of the ticket
    70  * '''cc''' - The list of email for notify the ticket change
     72 * '''owner''' - The person responsible for the ticket
     73 * '''cc''' - The list of emails for notifying about the ticket change
    7174
    7275'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''