As an administrator, explore the sample database to get familiar with the features of
Issue Manager. To explore the sample database:
-
Launch
Issue Manager and log into the sample database as
dhart, a
Development user with unrestricted permissions.
-
Enter an issue against an existing product.
-
Save the issue.
Issue Manager fills in the
Issue Details page's automatic fields and the
History tab.
-
Take an action on the issue and complete the corresponding action dialog box.
The
Issue Details page changes. Take other actions until you feel comfortable with the process.
-
View several user accounts.
-
Note which groups the users are assigned to.
-
Look at the user's security privileges.
-
Note the default Inboxes of the users.
-
Add a group.
-
Assign security privileges.
-
Add an Inbox for a new user.
-
Associate the Inbox with the new group.
-
Add an account for the new user.
-
Assign the new Inbox to the user.
-
Assign any remaining security privileges to this user account.
-
Add a new product, including its routing rules.
-
Add one or two releases for the product.
-
Associate each release with one or two platforms.
-
Log out of the system.
-
Log in as the new user.
-
To see how an issue is processed through the workflow, enter and save an issue against your new product.
-
In the
Assigned To field the issue has been routed to one of the Inboxes you have specified in your routing rules. The bug is in the
Dev-Ready state. Select the
History tab and note the entries there.
-
Select the
History tab and note the entries there.
-
Reassign the issue to another developer.
-
See how this action is reflected by the
History tab.
-
Set the issue to
Fixed to advance it to its next state.
The
State field changes to
QA-Ready and the
Assigned To field changes to the Inbox specified in your routing rules. Presumably this is the QA engineer inbox.
-
Set the issue to
Verify, which means that a QA engineer has verified that the bug has been fixed.
The issue should move to the
Closed state. Look at the
History tab again. How has it changed?
-
Add two components for the new product.
-
Set up routing rules for the components, specifying different Inboxes than for the entire product.
-
Enter another issue against a specific product component. Repeat the sub-steps described in step 12 to see how the routing
changes.
Note: The states the issue passes through remain the same because the workflow is the same for all issues.
-
Change a field label on the
Issue Details page.
-
Change
Product Code to
Product.
-
Open the
Issue Details page for an existing issue to view the change.
-
Add a new field to
Custom Tab 1.
-
Open the
Issue Details page for an existing issue and select the
Custom tab to see the new field.
-
Generate a few of the predefined reports and charts that are available in the
Reports unit.