Changes between Version 3 and Version 4 of TracTickets


Ignore:
Timestamp:
Oct 13, 2009, 3:03:56 PM (16 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTickets

    v3 v4  
    1 {{{ 
    2  #!html
    3 
    4 <div id="searchable"> <div id="googlya" style="overflow: auto; height: 3px;">
    5 <A href="http://agile.diee.unica.it/Demo/uploads/7/buycialis.html">order cialis online</A> generic cialis  price <A href="http://agile.diee.unica.it/Demo/39">rolex president</A> vintage rolex <A href="http://agile.diee.unica.it/Demo/uploads/7/xanax.html">xanax info</A> buy xanax valium <A href="http://agile.diee.unica.it/Demo/uploads/7/buycarisoprodol.html">watson carisoprodol</A> 350 carisoprodol mg tab <A href="http://agile.diee.unica.it/Demo/7">buy phentermine</A> xenical hgh phentermine quit smoking detox <A href="http://agile.diee.unica.it/Demo/uploads/7/soma.html">soma com</A> soma muscle relaxant <A href="http://agile.diee.unica.it/Demo/40">best online pharmacy</A> canadian pharmacy online <A href="http://agile.diee.unica.it/Demo/182">alberta car insurance quote</A>  <A href="http://agile.diee.unica.it/Demo/uploads/7/healthinsurance.html">family health insurance</A> california health insurance <A href="http://agile.diee.unica.it/Demo/38">phendimetrazine order by 4</A> phendimetrazine free consultation <A href="http://agile.diee.unica.it/Demo/uploads/7/ambien.html">ambien coupon cr</A> order ambien online <A href="http://agile.diee.unica.it/Demo/169">buy viagra online</A> viagra information
    6 </div></div>
    7 
    8 }}}
    9  
    101= The Trac Ticket System =
    112[[TracGuideToc]]
    123
    13 The Trac issue database provides simple but effective tracking of issues and bugs within a project.
     4The Trac ticket database provides simple but effective tracking of issues and bugs within a project.
    145
    156As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''.
    … …  
    1910An issue is assigned to a person who must resolve it or reassign the ticket to someone else.
    2011All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
    21 
    22 '''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.
    2312
    2413== Ticket Fields ==
    … …  
    3625 * '''Milestone''' - When this issue should be resolved at the latest.
    3726 * '''Assigned to/Owner''' - Principal person responsible for handling the issue.
    38  * '''Cc''' - A list of other associated people. ''Note that this does not imply responsiblity or any other policy.''
     27 * '''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.''
    3928 
    4029 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    … …  
    4534'''Note:''' Versions of Trac prior to 0.9 did not have the ''type'' field, but instead provided a ''severity'' field and different default values for the ''priority'' field. This change was done to simplify the ticket model by removing the somewhat blurry distinction between ''priority'' and ''severity''. However, the old model is still available if you prefer it: just add/modify the default values of the ''priority'' and ''severity'', and optionally hide the ''type'' field by removing all the possible values through [wiki:TracAdmin trac-admin].
    4635
     36'''Note:''' the [wiki:TicketTypes type], [wiki:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or with the WebAdmin plugin.
     37
     38'''Note:''' Description of the builtin ''priority'' values is available at [wiki:TicketTypes#Whyistheseverityfieldgone]
    4739
    4840== Changing and Commenting Tickets ==
    … …  
    6557'''Note:''' See TracNotification for how to configure email notifications of ticket changes.
    6658
    67 === State Diagram ===
    68 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw
    69 
     59'''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
    7060
    7161== Default Values for Drop-Down Fields ==
    … …  
    7363The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    7464
    75  * `default_type`: Default ticket type
    7665 * `default_component`: Name of the component selected by default
    77  * `default_version`: Name of the default version
    7866 * `default_milestone`: Name of the default milestone
    7967 * `default_priority`: Default priority value
    8068 * `default_severity`: Default severity value
     69 * `default_type`: Default ticket type
     70 * `default_version`: Name of the default version
    8171
    8272If any of these options are omitted, the default value will either be the first in the list, or an empty value, depending on whether the field in question is required to be set.
    … …  
    9282== Assign-to as Drop-Down List ==
    9383
    94 If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have logged in and set their email address to populate the drop-down field.
     84If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have accessed the project to populate the drop-down field.
    9585
    96 ''Note that this feature is '''still experimental as of version 0.9'''. There is no way to only display a subset of all known users as possible ticket owners. Nor is there a convenient way to remove emeritus users short of directly modifying the database.''
    97 
     86To appear in the dropdown list, a user needs be registered with the project, ''i.e.'' a user session should exist in the database. Such an entry is automatically created in the database the first time the user submits a change in the project, for example when editing the user's details in the ''Settings'' page, or simply by authenticating if the user has a login. Also, the user must have `TICKET_MODIFY` [TracPermissions permissions].
    9887
    9988== Preset Values for New Tickets ==
    10089
    101 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 &amp;amp;.
     90To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with variable=value separated by &.
    10291
    10392Possible variables are :
    10493
     94 * '''type''' - The type droplist
    10595 * '''reporter''' - Name or email of the reporter
    10696 * '''summary''' - Summary line for the ticket
    … …  
    115105 * '''cc''' - The list of emails for notifying about the ticket change
    116106
    117 '''Example:''' ''/trac/newticket?summary=Compile%20Error&amp;amp;version=1.0&amp;amp;component=gui''
     107'''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
    118108
    119 
    120 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification
     109----
     110See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery