1

Using JIRA for Issue and Project Tracking

Byron Chan

204/28/2010

Usability Issues with Bugzilla

Poor flow Overwhelming Certain types of searches hard (those

needed for defect counts on weekly status reports)

304/28/2010

Usability Issues with Bugzilla

Columns too close to each other Hard to differentiate severity and priority

404/28/2010

Tedious Project Management

Project Manager has to create and update project plan and progress report weekly

Hard to know project status – must ask each team member

504/28/2010

Use JIRA Instead

Well-known issue and project tracker User-friendly interface Highly customizable Allows plugins for additional functionality Downside

$4000 for academic license (unlimited users)Could purchase a $10 license (10 users) for

each team

604/28/2010

JIRA Search

List of search filters Grouped by category Easy date searches

704/28/2010

JIRA Search Results

Fields differentiated Icons/colors used Fields customizable

804/28/2010

Project Tracking in JIRA

Put project plan in JIRA as tasks/subtasks Team members responsible for updating Easy for PM to track

904/28/2010

JIRA Time Tracking

1004/28/2010

1104/28/2010

Many Other Features

Integrates with source control (Subversion, CVS, others)

IDE integration (Eclipse, Netbeans, others) Email threading Can import from Bugzilla

1204/28/2010

References

JIRA homepagehttp://www.atlassian.com/software/jira/

Bugzilla homepage http://www.bugzilla.org/

1304/28/2010

Questions?

1404/28/2010

Backup Slides

1504/28/2010

Academic Pricing

Source: http://www.atlassian.com/software/jira/pricing.jsp