Using JIRA for Issue
and Project Tracking
Byron Chan
1
Usability Issues with Bugzilla



04/28/2010
Poor flow
Overwhelming
Certain types of
searches hard
(those needed for
defect counts on
weekly status
reports)
2
Usability Issues with Bugzilla


04/28/2010
Columns too close to each other
Hard to differentiate severity and priority
3
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

04/28/2010
4
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
04/28/2010
5
JIRA Search



04/28/2010
List of search filters
Grouped by category
Easy date searches
6
JIRA Search Results



04/28/2010
Fields differentiated
Icons/colors used
Fields customizable
7
Project Tracking in JIRA
Put project plan in JIRA as tasks/subtasks
 Team members responsible for updating
 Easy for PM to track

04/28/2010
8
JIRA Time Tracking
04/28/2010
9
04/28/2010
10
Many Other Features
Integrates with source control (Subversion,
CVS, others)
 IDE integration (Eclipse, Netbeans, others)
 Email threading
 Can import from Bugzilla

04/28/2010
11
References

JIRA homepage
http://www.atlassian.com/software/jira/

Bugzilla homepage
http://www.bugzilla.org/
04/28/2010
12
Questions?
04/28/2010
13
Backup Slides
04/28/2010
14
Academic Pricing
Source: http://www.atlassian.com/software/jira/pricing.jsp
04/28/2010
15