Free Issue Tracking and Bug Tracking Systems: Updated 2010 Directory with a DevOps Evaluation Framework

Free issue trackers can be a strong fit for DevOps teams, but only when the tool matches your incident, bug, and service workflows. This revised guide preserves the original 2010 directory and adds a practical method to evaluate and pilot candidates safely.

Originally published on 2010-01-05; fully revised and updated.

What an issue tracking system covers

In the original post, an issue tracking system is described as software that manages lists of reported issues for customer support teams and internal teams. It can overlap with classic bug tracking and may also include a knowledge base for common resolutions.

• Track tickets from creation to resolution.
• Assign ownership and prioritize work.
• Support support-desk and engineering bug workflows.
• In some tools, provide web, email, or command-line interfaces.

A practical selection workflow for DevOps teams

Because this catalog is historical, use a structured selection process before adopting any tool in production.

flowchart TD
    A[Define use cases and ticket types] --> B[Set must have channels web email api]
    B --> C[Shortlist candidates from archive]
    C --> D[Validate docs activity and license]
    D --> E[Run pilot with real tickets]
    E --> F{Meets workflow reporting and access needs}
    F -- no --> C
    F -- yes --> G[Plan migration rollout and training]

Comparison of notable tools mentioned in the original post

The table below summarizes selected tools exactly in the spirit of the original descriptions. Treat this as a starting point, then verify current project status and documentation.

Quick commands to audit old project links

Before spending time on installation, quickly check whether candidate URLs are reachable.

urls=(
  "http://www.bugzilla.org/"
  "http://www.redmine.org/"
  "http://trac.edgewall.com/"
  "http://otrs.org/"
  "http://www.osticket.com/"
)

for url in "${urls[@]}"; do
  code=$(curl -L -s -o /dev/null -w "%{http_code}" "$url")
  printf "%-40s %s\n" "$url" "$code"
doneCode language: JavaScript (javascript)

Use this as a first pass only. A reachable URL does not confirm active maintenance, security posture, or suitability.

Full alphabetical list from the original post (archival)

This is the original-style directory preserved for reference, with minor wording cleanup. Verify each project independently before adoption.

A

• aDefHelpDesk — Open source DotNetNuke-based help desk module.
• Asset Tracker — Asset database and tracking tool with plugin-based integration options.
• Astres — PHP help desk tool with English and French translations.

B

• Bartley Helpdesk — Lightweight help desk for small to medium IT departments, includes inventory management.
• BATTS — Open source help desk designed for Linux/Unix command-line use with email interface.
• Big Help — Help desk portal built with Ruby on Rails.
• BugTracker.NET — ASP.NET/C# web-based bug or issue tracker with screenshot utility.
• Bugzilla — Perl-based bug tracking system, also usable for help desk support.

D

• DITrack — Bug and ticket system using Subversion as backend database; command-line interface in original description.
• Double Choco Latte — GNU enterprise package for call tracking and project management.

E

• eTicket Support — PHP-based electronic support ticket system.
• Eventum — Open source help desk package from the MySQL creators; PHP and MySQL based.

F

• Flyspray — Listed in the original post without additional description.

H

• Help Desk Lite — Simple issue tracking for service tickets and operator assignment.
• Help Desk Reloaded — PHP help desk with ticket prioritization, multi-technician support, and search.
• Helpdesk Issue Manager — Open source help desk tool running on PHP and PostgreSQL.

I

• Information Resource Manager — PHP-based help desk and asset tracker for IT departments.
• Information Resource Manager – GLPI Edition — Presented in the original post as IRM with additional enhancements.
• IssueTrackerProduct — Zope issue tracker focused on email communication and request management.
• itracker — Java-based open source help desk application emphasizing modularity and i18n support.

J

• JTrac — Java-based open source issue tracking system.
• Jutda Helpdesk — Django-powered ticket tracking system for small enterprise.

L

• Liberum Help Desk — Web-based help desk in ASP/VBScript with SQL Server or Access support.

M

• Mantis — PHP software bug and issue tracking system.

O

• One or Zero — Open source help desk software optimized for task-oriented help desks.
• OpenPsa — Full project system with help desk as one component.
• OpenCSM — Open source help desk solution with telephony component.
• OS Ticket — Lightweight ticket system designed for easy setup and use.
• OTRS — Trouble ticket system for telephone and email workflows across multiple departments.

P

• phpBugTracker — Web-based software bug tracker with layered architecture for customization.

R

• Redmine — Flexible project management web app built on Ruby on Rails.
• Request Tracker — Open source ticket tracking tool with email-centric workflow and web admin backend.
• Roundup — Issue tracker with command-line, web, and email interfaces.

S

• Savane — Web-based libre software hosting with issue tracking and role management.
• Sinergia — C# .NET framework for building customized help desk applications.
• SiT! Support Incident Tracker — SLA-aware support incident tracking system (PHP/MySQL).
• Slick Ticket — ASP ticket system with SQL Server and Active Directory support.
• Subissue — Stores issues within a Subversion repository; original post notes web UI in progress.
• SugarCRM Open Source — Primarily CRM, with light help desk capability.

T

• Trac — Minimalistic web-based project management and bug tracker with wiki features.
• Trouble Ticket Express — Web-based CGI help desk with MySQL and SQL Server support.

Z

No entries were listed under Z in the original post.

Common pitfalls when choosing a free tracker

• Picking a tool before mapping real ticket workflows (incident, problem, bug, service request).
• Assuming an old project list guarantees active maintenance.
• Skipping email intake, authentication, and permission model validation during pilot.
• Ignoring data export and migration strategy from day one.
• Not defining ownership, triage rules, and SLA expectations before rollout.

If you treat this list as an archive and combine it with disciplined evaluation, you can still use it to discover useful options quickly.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.