Changes between Version 4 and Version 5 of TracTickets


Ignore:
Timestamp:
Feb 1, 2017 12:38:00 AM (11 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTickets

    v4 v5  
    1 = The Trac Ticket System =
     1= The Trac Ticket System
    22[[TracGuideToc]]
    33
    4 The Trac ticket database provides simple but effective way to track issues and software bugs within a project.
     4The Trac ticket system provides a simple but effective way to track issues and software bugs within a project.
    55
    66As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''', '''software support issues''' among others.
    77
    8 As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible.
     8As with the TracWiki, this subsystem has been designed to make user contribution and participation as simple as possible.
    99
    1010An 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.
    1111
    1212[=#edit-permissions]
    13 However, a Trac installation may place restrictions on who can change what. For example, the default installation doesn't permit to non-authenticated users ("anonymous" users) to change anything, even to comment on an issue, for obvious spam prevention reasons. Check the local contributing policy, which you can usually find on the front page WikiStart, or contact your local Trac administrator.
     13However, a Trac installation may place restrictions on who can change what. For example, the default installation doesn't permit to non-authenticated users ("anonymous" users) to change anything, even to comment on an issue, for obvious spam prevention reasons. Check the local contributing policy, which you can usually find on the front page of WikiStart, or contact your local Trac administrator.
    1414
    15 == Ticket Fields ==
     15== Ticket Fields
    1616
    1717A ticket contains the following information:
    1818 
    1919 * '''Reporter''' — The author of the ticket.
    20  * '''Type''' — The category of the ticket. The default types are `defect`,  `enhancement` and `task`.
    21  * '''Component''' — The project module or subsystem this ticket concerns.
     20 * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`.
     21 * '''Component''' — The project module or subsystem that this ticket concerns.
    2222 * '''Version''' — Version of the project that this ticket pertains to.
    23  * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation.
    24  * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined.
    25  * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones.
     23 * '''Keywords''' — Keywords that a ticket is tagged with. Useful for searching and report generation.
     24 * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A dropdown list when multiple priorities are defined.
     25 * '''Milestone''' — Due date of when this issue should be resolved. A dropdown list containing the milestones.
    2626 * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
    27  * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.''
     27 * '''Cc''' — A comma-separated list of other users or email addresses to notify. Note that this does not imply responsibility or any other policy.
    2828 * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    2929 * '''Status''' — What is the current status? The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`.
     
    3838 - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
    3939
    40 == Changing and Commenting Tickets ==
     40== Changing and Commenting Tickets
    4141
    4242With appropriate permissions, as already mentioned [#edit-permissions above], a ticket entered into Trac can at any time be modified by '''annotating'''.
     
    4444Then, 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.
    4545
    46 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.
     46Comment 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.
    4747
    4848All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
    49 
    5049
    5150'''Notes:'''
     
    5655 - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
    5756
    58 == Default Values for Drop-Down Fields ==
     57== Default Values for Drop-Down Fields
    5958
    6059The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    6160
    62  * `default_component`: Name of the component selected by default
    63  * `default_milestone`: Name of the default milestone
    64  * `default_priority`: Default priority value
    65  * `default_severity`: Default severity value
    66  * `default_type`: Default ticket type
    67  * `default_version`: Name of the default version
     61 * `default_component`: Name of the component selected by default.
     62 * `default_milestone`: Name of the default milestone.
     63 * `default_priority`: Default priority value.
     64 * `default_severity`: Default severity value.
     65 * `default_type`: Default ticket type.
     66 * `default_version`: Name of the default version.
    6867 * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
    6968
    70 If 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.  Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section, others can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`.
     69If 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. Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section, others can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`.
    7170
    72 
    73 == Hiding Fields and Adding Custom Fields ==
     71== Hiding Fields and Adding Custom Fields
    7472
    7573Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through [wiki:TracAdmin trac-admin]. This of course only applies to drop-down fields, such as ''type'', ''priority'', ''severity'', ''component'', ''version'' and ''milestone''.
     
    7775Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.
    7876
     77== Assign-to as Drop-Down List
    7978
    80 == Assign-to as Drop-Down List ==
     79If 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 populate the list with all users who **have an authenticated session** and possess the `TICKET_MODIFY` [TracPermissions permissions].
    8180
    82 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 accessed the project to populate the drop-down field.
     81An authenticated session will be created the first time a user authenticates with the project. You can manually add an authenticated session using the ["TracAdmin#?session add" trac-admin] `session add` command. The `:1` suffix on the session id (i.e. username) is the key to creating an authenticated session:
     82{{{#!sh
     83trac-admin /path/to/projenv session add <sid>:1 [name] [email]
     84}}}
    8385
    84 To appear in the dropdown list, a user needs be registered with the project, ie 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].
     86You may find the dropdown list is //overpopulated// with users that are no longer active in the project. Revoking authentication privileges will not remove the session data that is used to populate the dropdown list. The [wiki:TracAdmin trac-admin] command can be used to list and remove sessions:
    8587
    86 '''Notes:'''
    87  - See [http://pacopablo.com/wiki/pacopablo/blog/set-assign-to-drop-down Populating Assign To Drop Down] on how to add user entries at database level.
     88 - List all sessions:
     89{{{#!sh
     90trac-admin /path/to/projenv session list
     91}}}
     92 - Remove a session:
     93{{{#!sh
     94trac-admin /path/to/projenv session delete SID
     95}}}
    8896
    89  - If you need serious flexibility and aren't afraid of a little plugin coding of your own, see [http://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo].
     97Alternatively, you can just revoke `TICKET_MODIFY` from users that you don't want to be included in the list. However, that will not be possible if you've granted `TICKET_MODIFY` to all //anonymous// or //authenticated// users.
    9098
    91  -  Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
     99'''Notes:'''
     100 - If you need more flexibility and aren't afraid of a little plugin coding of your own, see the [https://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo plugin].
     101 
     102 - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
    92103
    93 == Preset Values for New Tickets ==
     104== Preset Values for New Tickets
    94105
    95106To 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:
    96107
    97  * '''type''' — The type droplist
    98  * '''reporter''' — Name or email of the reporter
    99  * '''summary''' — Summary line for the ticket
    100  * '''description''' — Long description of the ticket
    101  * '''component''' — The component droplist
    102  * '''version''' — The version droplist
    103  * '''severity''' — The severity droplist
    104  * '''keywords''' — The keywords
    105  * '''priority''' — The priority droplist
    106  * '''milestone''' — The milestone droplist
    107  * '''owner''' — The person responsible for the ticket
    108  * '''cc''' — The list of emails for notifying about the ticket change
     108 * '''type''' — The type droplist.
     109 * '''reporter''' — Name or email of the reporter.
     110 * '''summary''' — Summary line for the ticket.
     111 * '''description''' — Long description of the ticket.
     112 * '''component''' — The component dropdown list.
     113 * '''version''' — The version dropdown list.
     114 * '''severity''' — The severity dropdown list.
     115 * '''keywords''' — The keywords or tags.
     116 * '''priority''' — The priority dropdown list.
     117 * '''milestone''' — The milestone dropdown list.
     118 * '''owner''' — The person responsible for the ticket.
     119 * '''cc''' — The list of emails for notifying about the ticket change.
    109120
    110 Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''
     121Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
    111122
    112123----
    113 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
     124See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery