1 / 12

Jira versus Bugzilla

Jira versus Bugzilla. t racking software issues - a change management exercise Chris De Spiegelaere Thiruvarangan Piranavam. Context. F ederal government department: Awesomeness Canada Medium-sized development project (15 team members) Mix of expert and intermediate developers

brigham
Download Presentation

Jira versus Bugzilla

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Jira versus Bugzilla tracking software issues - a change management exercise Chris De Spiegelaere ThiruvaranganPiranavam

  2. Context • Federal government department: Awesomeness Canada • Medium-sized development project (15 team members) • Mix of expert and intermediate developers • Ad hoc methods of change management • A tool to facilitate issue tracking and change management • Possible use of tool for future projects

  3. High-level goals • Facilitate change management • Controlled / rigorous process for resolving issues and tracking their progress • Aid in focusing maintenance and support through the entire project lifecycle • Decide on the best tool between Jira and Bugzilla

  4. Evaluation criteria (binary) • Must have • Integration with CVS • Integration with Eclipse • Ability to track individual issue progress • Ability to generate meaningful reports on project progress for project introspection • Bilingual (English / French)

  5. Evaluation criteria (out of 10) • Configurability for different projects (custom fields, different notification schemes, workflow) • Completeness of issue tracking capabilities • Ease of installation • Maintainability (maintenanceand administration) • Financial costs (value to tax payers) • Usability • Integration with other tools (multiple input / output methods, plugins…)

  6. Methodology • Installed and used for mock development projects • Scored tool out of ten points for each criterion • Add scores for each tool • Compare totals

  7. Bugzilla • Free and Open Source Software (MPL) • Well established and widely used • Primarily a defect tracking system https://landfill.bugzilla.org/bugzilla-4.0-branch/

  8. Bugzilla Evaluation

  9. Jira • Commercial product ($1000 - $8000) • Free for open source and non-profit • Wide usage • Used by many companies and open source projects (ASF uses Jira) • Issue tracking with project tracking elements http://jira.atlassian.com/chrisd/chrisd

  10. Jira Evaluation

  11. Summary and recommendation • Jira - 101 • Completeness of issue tracking • Ease of use • Granular configurability for multiple projects • Features are a super set of Bugzilla • Bugzilla – 95 • Free • Great for tracking defects

  12. Thanks! • Questions?

More Related