Mercurial > p > roundup > code

comparison doc/customizing.txt @ 3404:7d48c5b1e8f2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
merge from maint-0-8
author Richard Jones <richard@users.sourceforge.net>
date Mon, 15 Aug 2005 05:54:30 +0000
parents 7bc1e9c42a26
children 80dc8011228e
comparison
equal deleted inserted replaced
3401:62e4032cb280 3404:7d48c5b1e8f2
1 =================== 1 ===================
2 Customising Roundup 2 Customising Roundup
3 =================== 3 ===================
4 4
5 :Version: $Revision: 1.182 $ 5 :Version: $Revision: 1.183 $
6 6
7 .. This document borrows from the ZopeBook section on ZPT. The original is at: 7 .. This document borrows from the ZopeBook section on ZPT. The original is at:
8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx 8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
9 9
10 .. contents:: 10 .. contents::
939 Example Scenarios 939 Example Scenarios
940 ~~~~~~~~~~~~~~~~~ 940 ~~~~~~~~~~~~~~~~~
941 941
942 See the `examples`_ section for longer examples of customisation. 942 See the `examples`_ section for longer examples of customisation.
943 943
944 **anonymous access through the e-mail gateway**
945 Give the "anonymous" user the "Email Access", ("Edit", "issue") and
946 ("Create", "msg") Permissions but do not not give them the ("Create",
947 "user") Permission. This means that when an unknown user sends email
948 into the tracker, they're automatically logged in as "anonymous".
949 Since they don't have the ("Create", "user") Permission, they won't
950 be automatically registered, but since "anonymous" has permission to
951 use the gateway, they'll still be able to submit issues. Note that
952 the Sender information - their email address - will not be available
953 - they're *anonymous*.
954
944 **automatic registration of users in the e-mail gateway** 955 **automatic registration of users in the e-mail gateway**
945 By giving the "anonymous" user the "Email Registration" Role, any 956 By giving the "anonymous" user the ("Create", "user" Permission, any
946 unidentified user will automatically be registered with the tracker 957 unidentified user will automatically be registered with the tracker
947 (with no password, so they won't be able to log in through the web 958 (with no password, so they won't be able to log in through
948 until an admin sets their password). This is the default behaviour 959 the web until an admin sets their password). This is the default
949 in the tracker templates that ship with Roundup. 960 behaviour in the tracker templates that ship with Roundup. The new user
950 961 is given the Roles list defined in the "new_email_user_roles" config
951 **anonymous access through the e-mail gateway** 962 variable.
952 Give the "anonymous" user the "Email Access" and ("Edit", "issue")
953 Roles but do not not give them the "Email Registration" Role. This
954 means that when an unknown user sends email into the tracker, they're
955 automatically logged in as "anonymous". Since they don't have the
956 "Email Registration" Role, they won't be automatically registered, but
957 since "anonymous" has permission to use the gateway, they'll still be
958 able to submit issues. Note that the Sender information - their email
959 address - will not be available - they're *anonymous*.
960 963
961 **only developers may be assigned issues** 964 **only developers may be assigned issues**
962 Create a new Permission called "Fixer" for the "issue" class. Create a 965 Create a new Permission called "Fixer" for the "issue" class. Create a
963 new Role "Developer" which has that Permission, and assign that to the 966 new Role "Developer" which has that Permission, and assign that to the
964 appropriate users. Filter the list of users available in the assignedto 967 appropriate users. Filter the list of users available in the assignedto
1182 **login** 1185 **login**
1183 Determine whether the user has the "Web Access" Permission. 1186 Determine whether the user has the "Web Access" Permission.
1184 **logout** 1187 **logout**
1185 No permission checks are made. 1188 No permission checks are made.
1186 **register** 1189 **register**
1187 Determine whether the user has the "Web Registration" Permission. 1190 Determine whether the user has the ("Create", "user") Permission.
1188 **edit** 1191 **edit**
1189 Determine whether the user has permission to edit this item. If we're 1192 Determine whether the user has permission to edit this item. If we're
1190 editing the "user" class, users are allowed to edit their own details - 1193 editing the "user" class, users are allowed to edit their own details -
1191 unless they try to edit the "roles" property, which requires the 1194 unless they try to edit the "roles" property, which requires the
1192 special Permission "Web Roles". 1195 special Permission "Web Roles".
1193 **new** 1196 **new**
1194 Determine whether the user has permission to create this item. No 1197 Determine whether the user has permission to create this item. No
1195 additional property checks are made. Additionally, new user items may 1198 additional property checks are made. Additionally, new user items may
1196 be created if the user has the "Web Registration" Permission. 1199 be created if the user has the ("Create", "user") Permission.
1197 **editCSV** 1200 **editCSV**
1198 Determine whether the user has permission to edit this class. 1201 Determine whether the user has permission to edit this class.
1199 **search** 1202 **search**
1200 Determine whether the user has permission to view this class. 1203 Determine whether the user has permission to view this class.
1201 1204
Roundup Issue Tracker: http://roundup-tracker.org/