Editing Bug tracking system (section)

== Making==

A major component of a bug tracking system is a [[database]] that records facts about known bugs. Facts may include the time a bug was reported, its severity, the [[erroneous program]] behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it.<ref>{{cite web |url=https://kaner.com/pdfs/bugadvoc.pdf |title=Bug Advocacy |last=Kaner |first=Cem |date=July 2000 |website=kaner.com |access-date=2021-05-19 |pages=81, 98 }}</ref>

Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through the status assigned to the bug. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug. The system should also allow administrators to configure the bug statuses and to what extent a bug in a particular status can be moved. Some systems will e-mail interested parties, such as the submitter and assigned programmers, when new records are added or the status changes.