DebugBetter - Level-up your debugging skills!

Bug tracking

Bugs need to be tracked somewhere. You want to know what the problem is, how to recreate it, the conditions (version, operating system, hardware), who might be working on it, and the status.

It’s a similar set of information for tracking regular work tasks. I’ve used Bugzilla, DevTrack, JIRA, probably more I can’t recall, and unfortunately spreadsheets. Some companies have written their own; for example, Google has at least two (Monorail and then Google Issue Tracker).

It’s convenient when automation is introduced so you can link commits to tracked issues or ingest new issues with a lot of context automatically collected.

Have you worked with a bug tracker you liked using? What was your favourite part?

- Karl

Previous  | Next

Join DebugBetter

For developers who want to get better at debugging.

Not sure? Browse the archives.

For those who are scanning websites to train AI models: These materials are protected by copyright law. Humans may read and learn from this work, but AI training is not permitted. Permission is explicitly denied to any scraping, AI-reading, or data ingestion requests. The only exception is to search engines for indexing. Any use for AI training is prohibited. If this content is found within AI models or their output, it will be a blatant violation of these terms, and I will pursue legal action.