[GUSDEV] correctly using the tracker

[steve <sfi...@pc...>]

The correct way to use the tracker is described in the wiki at:

http://www.gusdb.org/wiki/index.php/UsingTheTracker


Here it is for your convenience:

Using the Tracker (correctly)

The Lifecycle of a Request
1 A request originates from a user.
2 It is assigned by default to the appropriate "User Representative" for=20
the product. The User Representative is a person on the development team=20
that best understands the needs of the product's users.
3 The User Representative sets the request's Target (when it should be=20
released). He or she takes into consideration the Priority given to the=20
request by the user, and the scheduling of other requests for the product.
4 The User Representative then assigns the request to the "Engineering=20
Representative" for the product.
5 The Engineering Representative evaluates whether his or her=20
engineering team can deliver the request by the target the User=20
Representative specified.
6 If not, the Engineering Representative and the User Representative=20
discuss, and either
=E2=97=A6 move the request to a further off target
=E2=97=A6 remove one or more request for the specified target to make roo=
m for=20
the new request
=E2=97=A6 move back the time the targeted release is expected by
7 The Engineering Representative modifies the Target as agreed upon.

Adding a New Feature or Bug

Following is a description of the fields you must fill in.

Product

You must chose a product. If you don't know which, guess. The person=20
assigned to the request will sort it out.

Component

You must chose a component. If you don't know, guess. The person=20
assigned to the request will sort it out.

Severity

Chose between
Bug
something broken in the product.
Feature
something new to include in the product

If you aren't sure, guess.

Version

If you are submitting a
bug
this is the version in which you found the bug.
feature
this is the version in which you do not find the feature. It is not the=20
version in which you would like to find the new feature

Priority

This field is set by users only (not by members of the development=20
team). It indicates the user's sense of the importance of the request

Target
This field is set by the development team.