/[web]/templates/bugzilla/trunk/admin/admin.html.tmpl
ViewVC logotype

Contents of /templates/bugzilla/trunk/admin/admin.html.tmpl

Parent Directory Parent Directory | Revision Log Revision Log


Revision 48 - (show annotations) (download)
Fri Nov 26 14:56:29 2010 UTC (13 years, 4 months ago) by dmorgan
File size: 7572 byte(s)
Add custom template with identity support
1 [%# The contents of this file are subject to the Mozilla Public
2 # License Version 1.1 (the "License"); you may not use this file
3 # except in compliance with the License. You may obtain a copy of
4 # the License at http://www.mozilla.org/MPL/
5 #
6 # Software distributed under the License is distributed on an "AS
7 # IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
8 # implied. See the License for the specific language governing
9 # rights and limitations under the License.
10 #
11 # The Original Code is the Bugzilla Bug Tracking System.
12 #
13 # Contributor(s): Frédéric Buclin <LpSolit@gmail.com>
14 #%]
15
16 [% PROCESS global/variables.none.tmpl %]
17
18 [% title = BLOCK %]
19 Administer your installation ([% terms.Bugzilla %]
20 [%+ constants.BUGZILLA_VERSION FILTER html %])
21 [% END %]
22
23 [% PROCESS global/header.html.tmpl title = title
24 style_urls = ['skins/standard/admin.css']
25 doc_section = "administration.html"
26 %]
27
28 <div>
29 This page is only accessible to empowered users. You can access administrative pages
30 from here (based on your privileges), letting you configure different aspects of
31 this installation. Note: some sections may not be accessible to you and are marked
32 using a lighter color.
33 </div>
34
35 <table>
36 <tr>
37 <td class="admin_links">
38 <dl>
39 [% class = user.in_group('tweakparams') ? "" : "forbidden" %]
40 <dt id="parameters" class="[% class %]"><a href="editparams.cgi">Parameters</a></dt>
41 <dd class="[% class %]">Set core parameters of the installation. That's the
42 place where you specify the URL to access this installation, determine how
43 users authenticate, choose which [% terms.bug %] fields to display, select
44 the mail transfer agent to send email notifications, choose which group of
45 users can use charts and share queries, and much more.</dd>
46
47 <dt id="preferences" class="[% class %]"><a href="editsettings.cgi">Default Preferences</a></dt>
48 <dd class="[% class %]">Set the default user preferences. These are the values
49 which will be used by default for all users. Users will be able to edit their
50 own preferences from the <a href="userprefs.cgi?tab=settings">Preferences</a>.</dd>
51
52 [% class = user.in_group('editcomponents') ? "" : "forbidden" %]
53 <dt id="sanitycheck" class="[% class %]"><a href="sanitycheck.cgi">Sanity Check</a></dt>
54 <dd class="[% class %]">Run sanity checks to locate problems in your database.
55 This may take several tens of minutes depending on the size of your installation.
56 You can also automate this check by running <tt>sanitycheck.pl</tt> from a cron job.
57 A notification will be sent per email to the specified user if errors are detected.</dd>
58
59 [% class = (user.in_group('editusers') || user.can_bless) ? "" : "forbidden" %]
60 <dt id="users" class="[% class %]"><a href="editusers.cgi">Users</a></dt>
61 <dd class="[% class %]">Create new user accounts or edit existing ones. You can
62 also add and remove users from groups (also known as "user privileges").</dd>
63
64 [% class = (Param('useclassification') && user.in_group('editclassifications')) ? "" : "forbidden" %]
65 <dt id="classifications" class="[% class %]"><a href="editclassifications.cgi">Classifications</a></dt>
66 <dd class="[% class %]">If your installation has to manage many products at once,
67 it's a good idea to group these products into distinct categories. This lets users
68 find information more easily when doing searches or when filing new [% terms.bugs %].</dd>
69
70 [% class = (user.in_group('editcomponents')
71 || user.get_products_by_permission("editcomponents").size) ? "" : "forbidden" %]
72 <dt id="products" class="[% class %]"><a href="editproducts.cgi">Products</a></dt>
73 <dd class="[% class %]">Edit all aspects of products, including group restrictions
74 which let you define who can access [% terms.bugs %] being in these products. You
75 can also edit some specific attributes of products such as
76 <a href="editcomponents.cgi">components</a>, <a href="editversions.cgi">versions</a>
77 and <a href="editmilestones.cgi">milestones</a> directly.</dd>
78
79 [% class = user.in_group('editcomponents') ? "" : "forbidden" %]
80 <dt id="flags" class="[% class %]"><a href="editflagtypes.cgi">Flags</a></dt>
81 <dd class="[% class %]">A flag is a custom 4-states attribute of [% terms.bugs %]
82 and/or attachments. These states are: granted, denied, requested and undefined.
83 You can set as many flags as desired per [% terms.bug %], and define which users
84 are allowed to edit them.</dd>
85
86 [% Hook.process('end_links_left') %]
87 </dl>
88 </td>
89
90 <td class="admin_links">
91 <dl>
92 [% class = user.in_group('admin') ? "" : "forbidden" %]
93 <dt id="custom_fields" class="[% class %]"><a href="editfields.cgi">Custom Fields</a></dt>
94 <dd class="[% class %]">[% terms.Bugzilla %] lets you define fields which are
95 not implemented by default, based on your local and specific requirements.
96 These fields can then be used as any other field, meaning that you can set
97 them in [% terms.bugs %] and run any search involving them.<br>
98 Before creating new fields, keep in mind that too many fields may make the user
99 interface more complex and harder to use. Be sure you have investigated other ways
100 to satisfy your needs before doing this.</dd>
101
102 <dt id="field_values" class="[% class %]"><a href="editvalues.cgi">Field Values</a></dt>
103 <dd class="[% class %]">Define legal values for fields whose values must belong
104 to some given list. This is also the place where you define legal values for some
105 types of custom fields.</dd>
106
107 <dt id="status_workflow" class="[% class %]"><a href="editworkflow.cgi">[%terms.Bug %] Status Workflow</a></dt>
108 <dd class="[% class %]">Customize your workflow and choose initial [% terms.bug %]
109 statuses available on [% terms.bug %] creation and allowed [% terms.bug %] status
110 transitions when editing existing [% terms.bugs %].</dd>
111
112 [% class = user.in_group('creategroups') ? "" : "forbidden" %]
113 <dt id="groups" class="[% class %]"><a href="editgroups.cgi">Groups</a></dt>
114 <dd class="[% class %]">Define groups which will be used in the installation.
115 They can either be used to define new user privileges or to restrict the access
116 to some [% terms.bugs %].</dd>
117
118 [% class = user.in_group('editkeywords') ? "" : "forbidden" %]
119 <dt id="keywords" class="[% class %]"><a href="editkeywords.cgi">Keywords</a></dt>
120 <dd class="[% class %]">Set keywords to be used with [% terms.bugs %]. Keywords
121 are an easy way to "tag" [% terms.bugs %] to let you find them more easily later.</dd>
122
123 [% class = user.in_group('bz_canusewhines') ? "" : "forbidden" %]
124 <dt id="whining" class="[% class %]"><a href="editwhines.cgi">Whining</a></dt>
125 <dd class="[% class %]">Set queries which will be run at some specified date
126 and time, and get the result of these queries directly per email. This is a
127 good way to create reminders and to keep track of the activity in your installation.</dd>
128
129 [% Hook.process('end_links_right') %]
130 </dl>
131 </td>
132 </tr>
133 </table>
134
135 [% PROCESS global/footer.html.tmpl %]

  ViewVC Help
Powered by ViewVC 1.1.30