close
Warning:
Can't synchronize with repository "(default)" (The repository directory has changed, you should resynchronize the repository with: trac-admin $ENV repository resync '(default)'). Look in the Trac log for more information.
- Timestamp:
-
2021-07-11T14:17:48-07:00 (3 years ago)
- Author:
-
trac
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v5
|
v6
|
|
2 | 2 | [[TracGuideToc]] |
3 | 3 | |
4 | | As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues''', among others. |
| 4 | As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues''', among others. |
5 | 5 | |
6 | 6 | As with the TracWiki, this subsystem has been designed to make user contribution and participation as simple as possible. Tickets can be edited, annotated, assigned, prioritized and discussed. |
… |
… |
|
12 | 12 | |
13 | 13 | A ticket contains the following information: |
14 | | |
| 14 | |
15 | 15 | * '''Summary''' — Simple text without WikiFormatting. |
16 | 16 | * '''Description''' — The body of the ticket. Accepts WikiFormatting. |
17 | 17 | * '''Reporter''' — The author of the ticket. |
18 | | * '''Type''' — The default types are `defect`, `enhancement` and `task`. |
| 18 | * '''Type''' — The default types are `defect`, `enhancement` and `task`. |
19 | 19 | * '''Component''' — The project module or subsystem that this ticket concerns. |
20 | 20 | * '''Version''' — Version of the project that this ticket pertains to. |
… |
… |
|
41 | 41 | All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket. |
42 | 42 | |
43 | | '''Note:''' |
| 43 | '''Note:''' |
44 | 44 | - TracLinks and WikiFormatting can be used in the ticket description and comments. Use TracLinks to refer to other issues, changesets and files. |
45 | 45 | |
… |
… |
|
85 | 85 | |
86 | 86 | '''Notes:''' |
87 | | - If you need more flexibility, you can subclass `ConfigurableTicketWokflow` and override the `get_allowed_owners` method. |
88 | | |
| 87 | - If you need more flexibility, then use subclass `ConfigurableTicketWorkflow` and override the `get_allowed_owners` method (see [trac:#12807 Trac ticket 12807]). |
| 88 | |
89 | 89 | - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page. |
90 | 90 | |
… |
… |
|
103 | 103 | * '''priority''' — The priority dropdown list. |
104 | 104 | * '''milestone''' — The milestone dropdown list. |
105 | | * '''owner''' — The person responsible for the ticket. |
106 | 105 | * '''cc''' — The list of emails for notifying about the ticket change. |
107 | 106 | |
108 | 107 | Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]` |
| 108 | |
| 109 | To set the ticket owner the workflow action may also need to be selected. For the [TracWorkflow#TicketCreateAction default workflow], the //create and assign// action can be selected with `action=create_and_assign` and the owner specified by assigning `action_create_and_assign_reassign_owner`. Alternatively, you could avoid needing to select the action by using the [TracWorkflow#BasicTicketWorkflowCustomization default attribute] to make //create and assign// the default action. |
| 110 | |
| 111 | For other custom workflow actions, determine the variable names by inspecting the `name` attribute of the //action// radio button and the //owner// input or select element. |
109 | 112 | |
110 | 113 | == Deleting Tickets #deleter |