UsingTheTracker

From GUS Wiki
Jump to: navigation, search

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 the product. The User Representative is a person on the development team that best understands the needs of the product's users.
  3. The User Representative sets the request's Target (when it should be released). He or she takes into consideration the Priority given to the request by the user, and the scheduling of other requests for the product.
  4. The User Representative then assigns the request to the "Engineering Representative" for the product.
  5. The Engineering Representative evaluates whether his or her engineering team can deliver the request by the target the User Representative specified.
  6. If not, the Engineering Representative and the User Representative discuss, and either
    • move the request to a further off target
    • remove one or more request for the specified target to make room for the new request
    • move back the time the targeted release is expected by
  1. 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 assigned to the request will sort it out.

Component |

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

Version |

   The  version you are using

Severity |

  Bug|
     something broken in the version of the product you are using
  Feature|
     something missing in the version of the product you are using
  Not sure |
     guess

Priority (set by users) |

   High|
       there is significant difficulty doing your work
   Medium|
     you could do your work more efficiently
   Low|
      you think this would help you do your work

Target (set by development team) |

   immediate release|
      immediately plan a release simply to get this fix out
   upcoming patch|
      include in the patch being worked on
   following patch|
     include in the patch planned after the upcoming patch
   upcoming release|
     include in the release being worked on
   following release|
     include in the release after the upcoming release
   near future release|
     include in a release within a few months
   far future release|
      include in a release at an indeterminate time, if ever