JIRA: Bug Tracking in GLAST

			Welcome to issue tracking in GLAST. We have adoped the JIRA ("jeera") issue/bug tracking tool. Our intent is to use this to track not only bugs but
to follow up on improvements and issues in our code system. Here are the initial thoughts on what we wanted from such a system.

[Organization | Getting Started | Reporting Issues | Working Issues | Watching Issues]

As of this writing, the JIRA czar is Johann Cohen-Tanugi. Johann will oversee that bugs and issues are, in fact, followed up.

Organization

Topics are separated into categories, projects and components, with categories cover ing Sim/Recon, ScienceTools, Infrastructure and Resources. Inside each of these are the various projects that comprise the big pieces.

Getting Started

You will need a JIRA account:

Go to the GLAST Confluence website's Dashboard page.

In the lower left corner, you will see a link inviting you to "sign up here".

Click on that link and fill out the Sign up form. You should receive an e-mail within 24 hours of signing up, indicating your account has been approved. (For more detailed information on JIRA, see JIRA: Bug Tracking in GLAST.)

Note: Your JIRA account also gives you access to Confluence, our knowledge management tool.

Once you have a JIRA account:

Go to the SAS JIRA ISSUE Summary Home page.

From "Children" section, select the Summary page you are interested in (e.g., Glast Release related issues, Infrastructure and Resources Related Issues, Science Tools Related Issues).

Reporting a Bug or Issue

Note that there are search tools to see if the bug you are reporting has already been input to the system.

select "create a new issue"	picked CAL in Simu/recon
described the request as an improvement	after creating the report.

Working an Issue

click on bug in question	Click on Resolve
after filling out the form, see the resolution	and you should get email that you resolved it, as does the submitter of the bug.

Watching Issues

Three tiers of notification have been created for each Category: users, developers and admins. They will be sent the following emails:

Project lead and admins get notified of all traffic.

Users get notified when there is a new issue created, and when it is resolved, as well as commented.

Developers receive all traffic but for the specific admin tasks: issue updated (this is just about modifying the status of the issue), issue closed or deleted..

Notes:

Johann has assigned membership in these groups; if you want a change, ask him.

You can also activate a "watch" on a given topic if it is of interest to you.

Click the "Watch It" link in the bottom left corner of the issue's details page.

Owned by: Richard Dubois

Last updated by: Chuck Patterson 07/30/2007