Bug tracker
Bugtracker (from English bug tracker , dt. About [Software] Error Tracker or lack followers ) are case processing systems (English issue tracking or trouble ticket system ) for the software development , which are used as a tool to program error to detect and document . They are also used to write status or feature reports - often interactively and on the Internet.
The term bug tracking refers to the process of troubleshooting per se (using debugging and trial and error methods ) and the process of tracking an error and its documentation over time.
more details
Bug trackers can improve communication between users and developers of computer programs. Often times, isolating a bug requires a series of questions and answers between users and programmers. Capturing this communication in a bug tracking system means central archiving and thus enables later research, e.g. B. with similar problems (as opposed to e-mail or telephone ).
In addition to program errors, bug trackers can also record suggestions for improvement and user requests or general processes. In some projects, for example, the term “metabugs” is used when an error or deficiency is an element of a task list. In other projects, the term "issues" is used instead, as this expression is not limited to program errors ( issue tracking system ).
Well-known free bug trackers are Bugzilla , Mantis , Phabricator , Roundup , Redmine , Trac and Flyspray . Well-known commercial bug trackers are Track + and Jira .
Motivations
Development departments that organize their problem recording in the form of simple problem documents or even e-mail collections have to contend with a number of problems; including z. B .:
- Only one person can make changes to the document at a time.
- If several people are involved, it requires more effort to compare the state of development.
- Only simple searches are possible.
- Organizing all problem documents is very tedious.
- The creation and maintenance of problem documents is associated with a great deal of manual effort.
- Tracking problems is very difficult, and problems that have already been recorded can be forgotten.
- Most of them are saved in proprietary formats, which makes it difficult or impossible to use on different platforms.
- Problem documents may not be accessible from everywhere. (see document releases, web access, etc.)
In contrast, bug trackers with a connected database can record answers to the following questions:
- What problems did you encounter?
- What are the problems?
- Which developer is responsible for the problem?
- Which program versions are affected?
- What has been done to correct the problem?
- What are the options to work around the problem?
- Has the problem really been resolved, i.e. retested?
- Has a problem reappeared once it has been solved?
- In which version of the program is the problem likely to be resolved?
- When is the problem likely to be resolved?
- How much effort is the solution likely to require?
- What was the actual effort?