Edgewall Software

Changes between Version 76 and Version 77 of TracTickets


Ignore:
Timestamp:
Dec 10, 2015, 11:13:28 AM (8 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TracTickets

    v76 v77  
    33[[TranslatedPages]]
    44
    5 The Trac ticket database provides a simple but effective way to track issues and software bugs within a project.
     5The Trac ticket system provides a simple but effective way to track issues and software bugs within a project.
    66
    77As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''', '''software support issues''' among others.
    … …  
    1212
    1313[=#edit-permissions]
    14 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.
     14However, 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.
    1515
    1616== Ticket Fields
    … …  
    1919 
    2020 * '''Reporter''' — The author of the ticket.
    21  * '''Type''' — The category of the ticket. The default types are `defect`,  `enhancement` and `task`.
     21 * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`.
    2222 * '''Component''' — The project module or subsystem this ticket concerns.
    2323 * '''Version''' — Version of the project that this ticket pertains to.
    2424 * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation.
    25  * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined.
    26  * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones.
     25 * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A dropdown list if different priorities are defined.
     26 * '''Milestone''' — Due date of when this issue should be resolved. A dropdown list containing the milestones.
    2727 * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
    28  * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.''
     28 * '''Cc''' — A comma-separated list of other users or email addresses to notify. Note that this does not imply responsibility or any other policy.
    2929 * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    3030 * '''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`.
    … …  
    4545Then, 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.
    4646
    47 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.
     47Comment 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.
    4848
    4949All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
    50 
    5150
    5251'''Notes:'''
    … …  
    6160The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    6261
    63  * `default_component`: Name of the component selected by default
    64  * `default_milestone`: Name of the default milestone
    65  * `default_priority`: Default priority value
    66  * `default_severity`: Default severity value
    67  * `default_type`: Default ticket type
    68  * `default_version`: Name of the default version
     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.
    6968 * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
    7069
    71 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`.
    72 
     70If 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`.
    7371
    7472== Hiding Fields and Adding Custom Fields
    … …  
    7876Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.
    7977
    80 
    8178== Assign-to as Drop-Down List
    8279
    83 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 populate the list with all users who **have an authenticated session** and possess the  `TICKET_MODIFY` [TracPermissions permissions].
     80If 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].
    8481
    85 An 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.
     82An 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:
    8683{{{#!sh
    8784trac-admin /path/to/projenv session add <sid>:1 [name] [email]
    8885}}}
     86
    8987You 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:
    9088
    … …  
    10199
    102100'''Notes:'''
    103 - 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].
    104 -  Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
     101 - 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].
     102 
     103 - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
    105104
    106105== Preset Values for New Tickets
    … …  
    108107To 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:
    109108
    110  * '''type''' — The type droplist
    111  * '''reporter''' — Name or email of the reporter
    112  * '''summary''' — Summary line for the ticket
    113  * '''description''' — Long description of the ticket
    114  * '''component''' — The component droplist
    115  * '''version''' — The version droplist
    116  * '''severity''' — The severity droplist
    117  * '''keywords''' — The keywords
    118  * '''priority''' — The priority droplist
    119  * '''milestone''' — The milestone droplist
    120  * '''owner''' — The person responsible for the ticket
    121  * '''cc''' — The list of emails for notifying about the ticket change
     109 * '''type''' — The type droplist.
     110 * '''reporter''' — Name or email of the reporter.
     111 * '''summary''' — Summary line for the ticket.
     112 * '''description''' — Long description of the ticket.
     113 * '''component''' — The component dropdown list.
     114 * '''version''' — The version dropdown list.
     115 * '''severity''' — The severity dropdown list.
     116 * '''keywords''' — The keywords or tags.
     117 * '''priority''' — The priority dropdown list.
     118 * '''milestone''' — The milestone dropdown list.
     119 * '''owner''' — The person responsible for the ticket.
     120 * '''cc''' — The list of emails for notifying about the ticket change.
    122121
    123 Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''
     122Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
    124123
    125124----
    126 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
     125See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery