1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
.. _optional-post-install-config:
Optional Post-Install Configuration
###################################
Bugzilla has a number of optional features. This section describes how
to configure or enable them.
.. _recurring-tasks:
Recurring Tasks
===============
Several of the below features require you to set up a script to run at
recurring intervals. The method of doing this varies by operating system.
Linux
-----
Run:
:command:`crontab -e`
This should bring up the crontab file in your editor. Add the relevant
cron line from the sections below in order to enable the corresponding
feature.
Windows
-------
Windows comes with a Task Scheduler. To run a particular script, do the
following:
#. :guilabel:`Control Panel` --> :guilabel:`Scheduled Tasks` -->
:guilabel:`Add Scheduled Task`
#. Next
#. Browse
#. Find :file:`perl.exe` (normally :file:`C:\\Perl\\bin\\perl.exe`)
#. Give the task a name, such as "Bugzilla <scriptname>"
#. Request the task be performed at your desired time and interval
#. If you're running Apache as a user, not as SYSTEM, enter that user
here. Otherwise you're best off creating an account that has write access
to the Bugzilla directory and using that
#. Tick "Open Advanced Properties.." and click Finish
#. Append the script name to the end of the "Run" field. eg
:command:`C:\\Perl\\bin\\perl.exe C:\\Bugzilla\\<scriptname>`
#. Change "start in" to the Bugzilla directory
.. _installation-bug-graphs:
Bug Graphs
==========
If you have installed the necessary Perl modules, as indicated by
:file:`checksetup.pl`, you can ask Bugzilla to regularly collect statistics
so that you can see graphs and charts.
On Linux, use a cron line as follows:
.. code-block:: none
5 0 * * * cd <your-bugzilla-directory> && ./collectstats.pl
On Windows, schedule the :file:`collectstats.pl` script to run daily.
After two days have passed you'll be able to view bug graphs from
the Reports page.
.. _installation-whining:
Whining
=======
Users can configure Bugzilla to annoy them at regular intervals, by having
Bugzilla execute saved searches at certain times and emailing the results to
the user. This is known as "Whining". The details of how a user configures
Whining is described in :ref:`whining`, but for it to work a Perl script must
be executed at regular intervals.
On Linux, use a cron line as follows:
.. code-block:: none
*/15 * * * * cd <your-bugzilla-directory> && ./whine.pl
On Windows, schedule the :file:`whine.pl` script to run every 15 minutes.
.. _installation-whining-cron:
Whining at Untriaged Bugs
=========================
It's possible for bugs to languish in an untriaged state. Bugzilla has a
specific system to issue complaints about this particular problem to all the
relevant engineers automatically by email.
On Linux, use a cron line as follows:
.. code-block:: none
55 0 * * * cd <your-bugzilla-directory> && ./whineatnews.pl
On Windows, schedule the :file:`whineatnews.pl` script to run daily.
Dependency Graphs
=================
Bugzilla can draw graphs of the dependencies (depends on/blocks relationships)
between bugs, if you install a package called :file:`dot`.
Linux
-----
Put the complete path to the :file:`dot` command (from the ``graphviz``
package) in the :param:`webdotbase` parameter. E.g. :paramval:`/usr/bin/dot`.
Windows
-------
Download and install Graphviz from
`the Graphviz website <http://www.graphviz.org/Download_windows.php>`_. Put
the complete path to :file:`dot.exe` in the :param:`webdotbase` parameter,
using forward slashes as path separators. E.g.
:paramval:`C:/Program Files/ATT/Graphviz/bin/dot.exe`.
Documentation
=============
Bugzilla has extensive documentation and help, written in
`reStructured Text <http://sphinx-doc.org/rest.html>`_
format. A generic compiled copy exists on
`bugzilla.readthedocs.org <https://bugzilla.readthedocs.org/>`_, and
:guilabel:`Help` links point to it by default. If you want to build and use a
local copy of the documentation, perhaps because you have added Bugzilla
extensions which come with documentation, or because your users don't have
Internet access from their machines, then:
* Install `Sphinx <http://sphinx-doc.org/>`_
(:file:`python-sphinx` package on Debian/Ubuntu)
Then run :command:`docs/makedocs.pl` in your Bugzilla directory.
Bugzilla will automatically detect that you've compiled the documentation
and link to it in preference to the copy on the Internet. Don't forget to
recompile it when you upgrade Bugzilla or install new extensions.
|
