170 likes | 372 Views
Using JIRA for Issue and Project Tracking. Byron Chan. Usability Issues with Bugzilla. Poor flow Overwhelming Certain types of searches hard (those needed for defect counts on weekly status reports). Usability Issues with Bugzilla. Columns too close to each other
E N D
Using JIRA for Issue and Project Tracking Byron Chan
Usability Issues with Bugzilla • Poor flow • Overwhelming • Certain types of searches hard (those needed for defect counts on weekly status reports)
Usability Issues with Bugzilla • Columns too close to each other • Hard to differentiate severity and priority
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
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
JIRA Search • List of search filters • Grouped by category • Easy date searches
JIRA Search Results • Fields differentiated • Icons/colors used • Fields customizable
Project Tracking in JIRA • Put project plan in JIRA as tasks/subtasks • Team members responsible for updating • Easy for PM to track
Many Other Features • Integrates with source control (Subversion, CVS, others) • IDE integration (Eclipse, Netbeans, others) • Email threading • Can import from Bugzilla
References • JIRA homepage http://www.atlassian.com/software/jira/ • Bugzilla homepage http://www.bugzilla.org/
Academic Pricing Source: http://www.atlassian.com/software/jira/pricing.jsp