PRepS Manuals | ||
---|---|---|
<<< Previous | Next >>> |
Several administrative tasks can be performed from within PRepS. These administrative tasks include project administration, user administration, setting up problem report attributes, and defining problem report queries. In order to perform administrative tasks, the user must be setup with administrator access.
Project administration tasks include creating new projects, assigning users to projects, determining what type of notification messages will be sent, and project version administration. All project administration tasks are performed via the Administration->Projects... menu item. Selecting Administration->Projects... from the menu displays the project list dialog. From there, users with administrator access can create new projects or update existing projects. Projects can also be deleted if problem reports have not been entered against it.
Pressing the Add, or View/Modify on the project list dialog displays the project edit dialog. The project edit dialog contains several tabs. The information Project Information tab includes the project name, the project description, the name of the project leader, and a flag indicating whether or not the project is active. The other tabs are used to add users to the project, determine which notification messages are sent, and setup project versions.
In order to use PRepS, you must create at least one project to submit problem reports against. To create new projects, follow these steps:
Display the project list dialog by selecting Administration->Projects... from the menu.
On the project list dialog, press the Add button to display the project edit dialog.
Fill in the Project Name text entry with a title for the project. A good title is one that is short but meaningful.
Describe the project in the Description text box.
Select a project leader from the Project Leader drop down list.
Go to the Submitters tab, and select at least one user. Technically this is optional. However, if you do not have any submitters selected, no one will be able to submit problem reports against the project. See Adding Users to Projects for details.
Go to the Project Members tab, and select at least one user. Technically this is optional. However, if you do not have any project members, you will not be able to assign problem reports for this project to anyone. See Adding Users to Projects for details.
Optionaly, go to the Notification Messages and select the notification messages you would like sent out for this project. Refer to Notification Messages for details.
Optionally, go to the Versions and setup some initial versions for thei project. See Project Versions for details.
There are two types of users that you can add to a project, submitters and project members. Submitters are users who are allowed to submit problem reports against a project. Project members are users who can have problem reports for a project assigned to them. You should have at least one submitter and one project member on any given project. PRepS allows you to have none, but will warn you about it, since it is not very useful to have projects without submitters or members.
To select submitters for a project, go to the Submitters tab on the project edit dialog. The Submitters tab contains a list of users setup in the current database. Select the users that you would like to allow to submit problem reports against the project. You can also use the Add All to select all currently defined users, or the Remove All to unselect all currently defined users.
Selecting project members is similar, except you go to the Project Members tab.
Notification messages are e-mail messages sent out by the database when certain events occur. There are three events that can trigger a notification message: a new problem report is entered against the project, a problem report against the project is assinged to someone, or the status of a problem report against the project is updated. The actual content of the messages is defined by template files that are distributed with libPRepS. See the PRepS Database Administration Manual (also distributed with libPRepS) for details on the message template files and their syntax.
Thre are four basic catagories of people who can receive notification messages:
The assingee is the person to whom the problem report being changed is assigned. The assignee can be sent a notification message upon the assignment of a problem report, and the update of a problem report's status.
Anyone who is listed as a project member or submitter for the project. The group can be sent a notification message upon the entry of a new problem report, or the update of a problem report's status.
The project leader of the project. The project leader can be sent a notification message upon the entry of a new problem report, the assignment of a problem report, and the update of a problem report's status.
The person who submitted the problem report that is being changed. The submitter can be sent a notification message upon the assignment of a problem report, and the update of a problem report's status.
To specify which notification messages should be sent for this project, select the Notification Messages tab on the project edit dialog. For each type of event, check the avaible sets of people who should receive a message.
PRepS allows you to setup version for projects. Project versions are used to track what version problem reports are entered against, and what version the problems are fixed in. Project versions are also important if you want to use PRepS to generate ChangeLogs for the project. To enter project version, select the Versions tab on the project edit dialog.
The version information list displays information about the versions that are current setup for this project.
By default, only active versions are displayed in the version information list. If the Show Inactive Versions check box is checked, inactive versions are also shown.
The version edit area consists of the Version text entry, Description text entry, Active check box, Add Version button, Modify Selected Version button, and Delete Selected Version button. This area is used to add, modify, and delete versions.
Enter the version name here. For example "1.2.4".
Enter a meaningful description of the version here.
If checked, the version being edited will be active, otherwise it will be inactive.
Use this button to create new versions. To create a new version from scratch, fill in the Version text and Description fields, then press this button to add the new version. To create a new version based on an existing version, select the desired existing version. The Version and Description text fields will get filled in with the existing version information. Modify the the Version and Description as desired (NOTE: you must modify the Version text). Press this button when you are ready to create the new version.
Use this button to modify existing versions. Select a version from the version list. The version information will be loaded into the edit area. Modify the version as required. Press this button to commit the modifications.
Use this button to delete existing versions. Select a version from the version list. The version information will be loaded into the edit area. Press this button to delete the version. Versions can only be deleted if the version is not used in any of the problem reports.
If a version is selected as the default opening version, that version is automatically selected in the new PR dialog when this project is selected. In other words, the selected version will be the version selected by default when entering problem reports against this project.
When problem reports are set to a closed status, the "fixed in" version will be set automatically to the default closing version if the "fixed in" version has not already been set.
<<< Previous | Home | Next >>> |
Reports | Up | User Administration |