Trac

Trac is a self-hosted bug tracker that pairs ticket management with an integrated wiki and a browser for Subversion and Git history. Its distinctive trait is how tightly those pieces interlock: a commit message can close a ticket, and the timeline view threads changesets, tickets and wiki edits into one chronological feed.

Why Trac instead of Jira

Jira keeps every ticket and workflow rule on Atlassian's servers, and its per-user pricing grows the bill with headcount even for occasional users. Trac runs as a single Python application on hardware or a container you control, so client bug reports and repository history for a confidential codebase never leave your network. For an agency handling clients' source under NDA, or an ops team that needs an audit trail it fully owns, that outweighs Jira's automation rules or marketplace apps.

The trade-off is real: Jira's board views, custom workflow states and hundreds of third-party integrations have no equivalent in Trac's core. Each Trac instance is also scoped to one project environment — running five projects means standing up five separate environments, not one shared workspace with per-project boards. Teams that need cross-project reporting or SSO should expect to build those themselves.

What it does well

• Wiki markup works inside ticket descriptions, commit messages and wiki pages alike, so a bug report and a changelog entry read the same way.
• The timeline view chains tickets, wiki edits and commits chronologically, which makes reconstructing what happened last week fast without cross-referencing tools.
• Native Subversion and Git browsing puts diffs and blame one click from the ticket that references them, with no separate code-review tool to license.
• Custom ticket fields and report queries are configured through plain-text config and a SQL-like TracQuery syntax, which suits ops leads comfortable editing config over clicking wizards.
• A milestone and roadmap view gives a lightweight release plan without importing a full project-management suite.
• Runs on SQLite for a small team or Postgres/MySQL once several people hit it at once, so the ops footprint grows with the team.

Limitations

• Public ticket submission is notoriously unfriendly — a widely shared 2019 Hacker News thread called it the hardest part of the tool to use, citing Django's own Trac instance as an example.