Fundamentals of Software Bug Tracking and Management

This article provides a basic overview of software testing fundamentals, emphasizing defect management tools ranging from early QC systems to Redmine, Bugzilla, and modern JIRA, and explains that mastering one tool helps understand others.

It outlines essential prerequisites for reproducing bugs, such as the operating system, browser environment, and other system-specific conditions that must be documented.

The piece describes common JIRA issue types—including Bug, Case, Enhancement, Epic, Folder, Story, Task (and Sub‑task), Tech Note, and Usability Issue—highlighting how JIRA serves as more than just a defect tracker.

Three classification schemes for bug types are presented: module‑based (e.g., Home, Data, Share), error‑type based (e.g., code error, design flaw, UI optimization), and category‑based (function, performance, UI, usability, compatibility, others).

Severity levels are defined in four tiers: Fatal, Critical, Major, and Minor, each describing the impact on system operation and data security.

Priority levels (Low, Medium, High, Urgent) are discussed, noting that severity does not always dictate priority and providing examples where a low‑severity issue may still require urgent attention.

The bug status lifecycle in JIRA is detailed: New, Open, In‑progress, Resolved, Reopened, and Closed, indicating the responsible parties at each stage.

A comprehensive bug handling process is outlined, covering creation (including detailed reproduction steps and attributes), assignment (direct or via project lead), confirmation by developers, fixing, possible postponement, regression testing, and final closure.

Finally, the author notes the effort put into compiling the article and invites readers to like and share.