0
1.0
Like milestones we can assign a date to a version, which we should think of as the
release date.
The usual commands show up here with rename, add, and remove being
supplemented by time, which behaves much like due and completed do
for milestones.
Customizing Default Values
When a ticket is created, most fields have a default value. Like the pre-determined
fields though, we can customize this. Default values are controlled by the file
/projects/trac/
/conf/trac.ini. In that file there is a ticket
section as follows:
[ticket]
default_component =
default_milestone =
default_priority = major
default_type = defect
default_version =
restrict_owner = false
If we change this section, the next ticket created after we have saved it will reflect
the changes.
Tracking Our Tasks
[ 54 ]
Viewing Tickets
Although we have already seen what a ticket looks like when we view it directly,
we are yet to explore the ticket reporting capabilities of Trac. If we click the View
Tickets link in Trac's main menu, we will be taken to the list of default reports.
Clicking on any one of these reports will provide us with the summary information
of each ticket that matches the report's filter.
The list of default reports should suffice for most requirements, but if they do not we
have a custom query builder available so we can write our own.
Pages:
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81