This release of the Track+ application supports most commonly occurring administrative tasks via the Web interface. For requirements that go beyond these supported tasks the administrator has to employ the tools that come with the RDBMS, e.g. the "mysql" command line interpreter for MySQL or the "IBConsole" utility for Firebird and Interbase. To support manual SQL commands, the database structure is illustrated at the end of the document. It is beyond the scope of this manual to teach how to issue SQL statements against a database.
The tasks most common to occur will be to add a new project with subsystems, classes, and releases. The tables of a more static nature such as states, categories, etc. can not yet be administrated via the web interface. However, modifying these tables is a task rarely done.
The Track+ application comes with a predefined user "admin", password "tissi" installed as the system administrator. The password and email of this user should be changed when first using the system.
The admin user has access to all project administration access management pages. It should be her privilege to add new projects. Each project itself may have several project specific administrators out of the regular user base. These project specific administrators have the same rights as the admin user, except that these rights are limited to specific projects.
It is possible to add more system administrators by manually (via SQL) inserting users into the TPERSON table and giving them a user key of less than 100.
Only system administrators will have access to the site administration pages. Project administrators (see below) will have access to the project administration pages for those projects that they have administration privileges for.
There are special web pages that can be accessed if a person is registered as a system administrator, or has been granted administrator rights for a specific project. When recognized as an project administrator, one can modify projects via these web pages. These pages are accessible via the "Administration" tab on the main menu and then the "Project Admin." tab. Initially, only the system administrator "admin" has access to these pages.
Any user can be promoted to administrator for the entire system and all projects by changing her user id to a number below 100. This should only be done to users freshly registered. The regular way of setting up project administrators is described in the next chapter.
The project list contains all projects the logged on user is registered as an administrator. Any of Subsystem, Release, and Class can be added by writing in the appropriate field below the lists and pressing the add button. Selecting an item from the list, writing some text in the edit field, and pressing the "Edit" button changes that list entry to the new value. A selected item can also be deleted if it isn't used any more in any issue. Thus, it is not possible for instance to deleted entire releases if there are issues that pertain to that release, even if they have been closed.
Deleting entire projects requires to first move or delete all issues pertaining to these projects. This has to be done via manual SQL statements or issue for issue via the application. Only the Track+ system administrator can delete and add projects.
For each project, there is a default manager that receives all issues unless the person entering an issue chooses a different person. The default owner should be selected from the list presented under the "Project:" list.
Each project belongs to a "project type". Project types may for example be
development project
procurement projects
field trial projects
rollout project
or just projects in different departments. Project types carry with them specific properties, for example workflows. Thus you can define a set of workflows once, and they will be used by all projects of this project type.