Scarab has a very dynamic issue management strategy. Committing, tracking and modifying issues is a simple process. Scarab has the following issue management features:
Issue types provide a unique set of attributes and options used to describe issues in a meaningful manner. Attributes within an issue type are defined by the project administrator and affect only issues within that issue type. Each project has a unique set of issue types. You may have a different set of permissions for each issue type in your project. Issues remain within the issue type in which they are entered until a user moves or copies them to another issue type.
Before you enter issues for your project, you should familiarize yourself with the available set of issue types. Where you enter an issue will be determined by how your project is organized. Once you have selected the issue type that best describes your issue, click on the name of the issue.
Attributes are the common descriptors for issues. Attributes are used to categorize issues for tracking, comparative and rate of change analysis. Each issue type has a unique set of attributes like Summary, Description, Milestone, Priority, Status, Resolution and Severity. There is a default set of values for the attributes but your project administrator may have altered the set available for your issue type.
Attributes can be organized in groups. If duplication checking is active, you enter a subset of attributes for the issue. This subset is used to check for duplicates in the database. After the duplication checking process is complete, you can enter values for the remaining attributes.
An issue type may have a set of required attributes. Values for the required attributes must be entered before committing the issue. Required attributes are identified by an asterisks (*) beside the name of the attribute.
On many results pages you can change which attributes appear on your screen. For information on customizing your interface see customizing the screen..
After selecting your issue type and the Enter new link from the left navigation you can enter values for the available attributes. Each attribute will have either a drop down box with options to select from or a text entry form for you to enter text. All attributes with an asterisks (*) beside the title must have values before saving the issue.
If duplication tracking is active, entering an issue becomes a three step process. The first step is to define a subset of attributes that will be used to check for duplicates in the database once you have used the Next button. The second step is to review all possible duplicates and determine what action to perform (see Duplicates for more information on duplicate management). The third step is to enter values for the remaining attributes.
While you are entering the issue you can attach a relevant file using the same form. Attaching a file helps you and others to easily share relevant information or patches. For more information on adding attachments see Attachments.
Before submitting your issue you can select where in the application you would like to go next. Each option submits the issue and takes you to one of the following functional areas: