Bug tracking system
Bugtracker (Eng. " [Software ] Error Tracker " ) are case management systems (English issuetracking or trouble ticket system) for software development, which are used as a tool to detect bugs and documented. Also state or feature blogs written - with them - often interactively and on the Internet.
Bugtracker can improve communication between users and developers of computer programs. Often the limitation of a program error requires a sequence of questions and answers between users and programmers. Detection of this communication in a bug tracking system is a central archiving, enabling subsequent searches, eg with similar problems (as opposed to e-mail or phone).
Besides bugs bug tracker can record suggestions and wishes of users or general operations. For some projects, then one speaks, for example, of " Metabugs " where a bug is an element in a task list. In other projects, we speak instead of " Issues " ( affairs, operations ), since this expression not only on bugs limited ( issue tracking system ).
The term refers to a bug tracking the process of troubleshooting (through methods of debugging and trial and error ), on the other hand the operation to pursue a mistake together with its documentation over time.
Development departments that organize their problem identification in the form of simple issue documents or even simple email - collections have to contend with a number of problems; including, for example:
- It can always make only one person changes to the document.
- If several people are involved, it requires increased effort to match the level of development.
- There are only simple queries possible.
- An organization of all documents problem is very troublesome.
- Creation and maintenance of problem documents is associated with very high and manual effort.
- The tracking of problems is very difficult, which is already recognized problems can be forgotten.
- Most is stored in proprietary formats, making it difficult to use on different platforms or impossible.
- Problem documents are not accessible from anywhere policy. (see document sharing, web access, etc.)
By contrast can be recorded in issue tracker database has been connected with answers to the following questions:
- What problems are you having?
- What kind of problems?
- Which developer is responsible for the problem?
- What versions are affected?
- What has been done to fix the problem?
- What are the options to get around the problem?
- Is the problem really fixed, so retested?
- Is a once solved problem resurfaced?
- In which version of the program, the problem is expected to be fixed?
- When will be expected to fix the problem?
- How much effort is expected to require the solution?
- What was the actual cost?