Mercurial > p > roundup > code
diff doc/customizing.txt @ 6174:5522c950a2e4
Add indexing for roundup-admin references.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 16 May 2020 13:40:12 -0400 |
| parents | 53a674b5910f |
| children | a701c9c81597 |
line wrap: on
line diff
--- a/doc/customizing.txt Sat May 16 13:39:47 2020 -0400 +++ b/doc/customizing.txt Sat May 16 13:40:12 2020 -0400 @@ -1004,6 +1004,8 @@ setkey(property) ~~~~~~~~~~~~~~~~ +.. index:: roundup-admin; setting assignedto on an issue + Select a String property of the class to be the key property. The key property must be unique, and allows references to the items in the class by the content of the key property. That is, we can refer to users by @@ -1738,7 +1740,7 @@ # db.security.addPermissionToRole('Anonymous', 'Edit', cl) .. index:: - single: roundup-admin; class permissions + single: roundup-admin; view class permissions You can use ``roundup-admin security`` to verify the permissions defined in the schema. It also verifies that properties specified in @@ -4031,9 +4033,10 @@ Populating the new category class ::::::::::::::::::::::::::::::::: -If you haven't initialised the database with the ``roundup-admin`` -"initialise" command, then you can add the following to the tracker -``initial_data.py`` under the comment:: +If you haven't initialised the database with the +"``roundup-admin initialise``" command, then you +can add the following to the tracker ``initial_data.py`` +under the comment:: # add any additional database creation steps here - but only if you # haven't initialised the database with the admin "initialise" command @@ -4045,6 +4048,8 @@ category.create(name="chaco") category.create(name="weave") +.. index:: roundup-admin; create entries in class + If the database has already been initalised, then you need to use the ``roundup-admin`` tool::
