913:
109:) to keep track of issues communicated to software developers. Using an LBT allows support professionals to track bugs in their "own language" and not the "language of the developers." In addition, an LBT allows a team of support professionals to track specific information about users who have called to complain—this information may not always be needed in the actual development queue. Thus, there are two tracking systems when an LBT is in place.
80:
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
89:
The main benefit of a bug-tracking system is to provide a clear centralized overview of development requests (including both bugs and improvements; the boundary is often fuzzy), and their state. The prioritized list of pending items (often called backlog) provides valuable input when defining the
93:
In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results because different bugs may have different levels of severity and complexity. The severity of a bug may not be
81:
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.
163:
can also be used as a distributed bug tracker. It can manage documents and code as well, in an integrated distributed manner. However, its query functionality is not as advanced or as user-friendly as some other, non-distributed bug trackers such as
60:
A bug tracking system is usually a necessary component of a professional software development infrastructure, and consistent use of a bug or issue tracking system is considered one of the "hallmarks of a good software team".
409:
121:. This approach allows including bug tracking and fixing in a general product development process, fixing bugs in several product versions, automatic generation of a product
77:
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.
230:
137:
software. These distributed bug trackers allow bug reports to be conveniently read, added to the database or updated while a developer is offline.
335:
459:
208:
188:
and IBM Rational
Quality Manager come with their own bug tracking systems, other tools integrate with popular bug tracking systems.
943:
917:
49:
projects, allow end-users to enter bug reports directly. Other systems are used only internally in a company or organization doing
365:
953:
922:
202:
94:
directly related to the complexity of fixing the bug. There may be different opinions among the managers and architects.
893:
452:
197:
414:
445:
134:
17:
602:
234:
145:
118:
54:
73:
that records facts about known bugs. Facts may include the time a bug was reported, its severity, the
373:
552:
39:
257:
767:
670:
181:
50:
46:
31:
8:
830:
775:
708:
423:
948:
542:
752:
612:
185:
138:
74:
102:
159:
and bug tracking systems are conventionally viewed as distinct types of software,
698:
647:
532:
404:
343:
122:
937:
744:
582:
490:
399:
152:, for example, enables this functionality via the source-control tool, Kiln.
117:
Bug and issue tracking systems are often implemented as a part of integrated
144:
Recently, commercial bug tracking systems have also begun to integrate with
810:
427:
35:
800:
592:
432:
437:
279:
873:
678:
106:
883:
850:
840:
718:
632:
522:
308:
169:
165:
70:
38:
in software development projects. It may be regarded as a type of
688:
572:
508:
313:
160:
149:
112:
863:
655:
418:
622:
498:
105:
used by a team of application support professionals (often a
820:
562:
156:
53:. Typically bug tracking systems are integrated with other
27:
Software application that track of reported software bugs
45:
Many bug tracking systems, such as those used by most
141:
and
Veracity both include distributed bug trackers.
90:
product road map, or maybe just "the next release".
175:
30:A tracking system or defect tracking system is a
935:
477:Years indicate the date of first stable release.
69:A major component of a bug tracking system is a
306:
133:Some bug trackers are designed to be used with
300:
228:
453:
113:Part of integrated project management systems
255:
172:, although it is not wiki software as such.
128:
460:
446:
433:List of distributed bug tracking software
363:
209:Comparison of project management software
467:
408:) is being considered for deletion. See
366:"Integrated issue tracking with Ikiwiki"
168:. Similar statements can be made about
14:
936:
357:
441:
277:
231:"Implement Client-side Bug Reporting"
229:Bogomil Shopov (September 8, 2014).
203:Comparison of issue-tracking systems
24:
25:
965:
412:to help reach a consensus. ›
391:
256:Joel Spolsky (November 8, 2000).
912:
911:
307:Jonathan Corbet (May 14, 2008).
211:– Including bug tracking systems
205:– Including bug tracking systems
198:Application lifecycle management
176:Bug tracking and test management
944:Bug and issue tracking software
424:How to Report Bugs Effectively
328:
271:
249:
222:
13:
1:
397:
215:
34:that keeps track of reported
135:distributed revision control
7:
954:Project management software
191:
146:distributed version control
55:project management software
10:
970:
364:Joey Hess (6 April 2007).
309:"Distributed bug tracking"
119:project management systems
907:
793:
766:
743:
736:
669:
646:
489:
482:
475:
64:
410:templates for discussion
278:Kaner, Cem (July 2000).
129:Distributed bug tracking
84:
258:"Painless Bug Tracking"
99:local bug tracker (LBT)
681:(formerly TestTrack) (
894:Azure DevOps Services
415:Bug Tracking Software
182:test management tools
40:issue tracking system
469:Bug tracking systems
51:software development
47:open-source software
32:software application
776:Azure DevOps Server
709:Azure DevOps Server
237:on 13 November 2014
125:and release notes.
336:"FogBugz Features"
180:While traditional
931:
930:
789:
788:
732:
731:
613:Apache Bloodhound
289:. pp. 81, 98
186:HP Quality Center
75:erroneous program
16:(Redirected from
961:
915:
914:
899:
889:
879:
869:
860:
856:
846:
836:
826:
816:
806:
781:
758:
741:
740:
724:
714:
704:
694:
684:
661:
638:
628:
618:
608:
598:
588:
578:
568:
558:
548:
538:
528:
518:
514:
504:
487:
486:
462:
455:
448:
439:
438:
385:
384:
382:
380:
370:NetworkWorld.com
361:
355:
354:
352:
351:
342:. Archived from
332:
326:
325:
323:
321:
304:
298:
297:
295:
294:
284:
275:
269:
268:
266:
264:
253:
247:
246:
244:
242:
233:. Archived from
226:
103:computer program
21:
969:
968:
964:
963:
962:
960:
959:
958:
934:
933:
932:
927:
903:
897:
887:
877:
867:
858:
854:
844:
834:
824:
814:
804:
785:
779:
762:
756:
728:
722:
712:
702:
692:
682:
665:
659:
642:
636:
626:
616:
606:
596:
586:
576:
566:
556:
546:
536:
533:Request Tracker
526:
516:
512:
502:
478:
471:
466:
413:
394:
389:
388:
378:
376:
362:
358:
349:
347:
334:
333:
329:
319:
317:
305:
301:
292:
290:
282:
276:
272:
262:
260:
254:
250:
240:
238:
227:
223:
218:
194:
178:
131:
115:
87:
67:
28:
23:
22:
15:
12:
11:
5:
967:
957:
956:
951:
946:
929:
928:
926:
925:
920:
908:
905:
904:
902:
901:
891:
881:
871:
861:
848:
838:
828:
818:
808:
797:
795:
791:
790:
787:
786:
784:
783:
772:
770:
764:
763:
761:
760:
749:
747:
738:
734:
733:
730:
729:
727:
726:
716:
706:
696:
686:
675:
673:
667:
666:
664:
663:
652:
650:
644:
643:
641:
640:
630:
620:
610:
600:
590:
580:
570:
560:
550:
540:
530:
520:
506:
495:
493:
484:
480:
479:
476:
473:
472:
465:
464:
457:
450:
442:
436:
435:
430:
421:
393:
392:External links
390:
387:
386:
356:
327:
299:
280:"Bug Advocacy"
270:
248:
220:
219:
217:
214:
213:
212:
206:
200:
193:
190:
177:
174:
130:
127:
123:knowledge base
114:
111:
86:
83:
66:
63:
26:
9:
6:
4:
3:
2:
966:
955:
952:
950:
947:
945:
942:
941:
939:
924:
921:
919:
910:
909:
906:
895:
892:
885:
882:
875:
872:
865:
862:
852:
849:
842:
839:
832:
829:
822:
819:
812:
809:
802:
799:
798:
796:
792:
777:
774:
773:
771:
769:
765:
754:
751:
750:
748:
746:
745:Free software
742:
739:
735:
720:
717:
710:
707:
700:
697:
690:
687:
680:
677:
676:
674:
672:
668:
657:
654:
653:
651:
649:
645:
634:
631:
624:
621:
614:
611:
604:
601:
594:
591:
584:
583:Apache Allura
581:
574:
571:
564:
561:
554:
551:
544:
541:
534:
531:
524:
521:
510:
507:
500:
497:
496:
494:
492:
491:Free software
488:
485:
483:Client-server
481:
474:
470:
463:
458:
456:
451:
449:
444:
443:
440:
434:
431:
429:
425:
422:
420:
416:
411:
407:
406:
401:
396:
395:
375:
371:
367:
360:
346:on 2013-07-05
345:
341:
337:
331:
316:
315:
310:
303:
288:
281:
274:
259:
252:
236:
232:
225:
221:
210:
207:
204:
201:
199:
196:
195:
189:
187:
183:
173:
171:
167:
162:
158:
153:
151:
147:
142:
140:
136:
126:
124:
120:
110:
108:
104:
101:is usually a
100:
95:
91:
82:
78:
76:
72:
62:
58:
56:
52:
48:
43:
41:
37:
36:software bugs
33:
19:
859:discontinued
811:GNU Savannah
468:
428:Simon Tatham
403:
377:. Retrieved
369:
359:
348:. Retrieved
344:the original
339:
330:
318:. Retrieved
312:
302:
291:. Retrieved
286:
273:
261:. Retrieved
251:
239:. Retrieved
235:the original
224:
179:
154:
143:
132:
116:
98:
96:
92:
88:
79:
68:
59:
44:
29:
18:Bug tracking
801:SourceForge
768:Proprietary
737:Distributed
671:Proprietary
398:‹ The
379:10 November
340:Fogbugz.com
241:17 November
938:Categories
923:Comparison
350:2010-10-29
293:2021-05-19
263:29 October
216:References
949:Help desk
874:Bitbucket
831:Launchpad
679:Helix ALM
648:Open-Core
593:Maniphest
320:7 January
287:kaner.com
155:Although
107:help desk
918:Category
884:YouTrack
851:CodePlex
841:Assembla
719:YouTrack
633:Codeberg
543:MantisBT
523:Bugzilla
400:template
192:See also
184:such as
170:org-mode
166:Bugzilla
71:database
689:Axosoft
573:Redmine
553:Roundup
509:Debbugs
402:below (
314:LWN.net
161:ikiwiki
150:FogBugz
916:
864:GitHub
794:Hosted
753:Fossil
656:GitLab
603:Tuleap
419:Curlie
405:Curlie
139:Fossil
65:Making
623:Gitea
499:GNATS
283:(PDF)
157:wikis
85:Usage
898:2012
888:2011
878:2008
868:2008
855:2006
845:2005
835:2004
825:2002
821:OSDN
815:2000
805:1999
780:2013
757:2006
723:2009
713:2005
703:2002
699:Jira
693:2002
683:1998
660:2011
637:2019
627:2016
617:2012
607:2011
597:2010
587:2009
577:2006
567:2004
563:Trac
557:2001
547:2000
537:1999
527:1998
517:1999
513:1994
503:1992
381:2014
322:2009
265:2010
243:2014
426:by
417:at
374:IDG
148:.
940::
857:)
515:/
372:.
368:.
338:.
311:.
285:.
97:A
57:.
42:.
900:)
896:(
890:)
886:(
880:)
876:(
870:)
866:(
853:(
847:)
843:(
837:)
833:(
827:)
823:(
817:)
813:(
807:)
803:(
782:)
778:(
759:)
755:(
725:)
721:(
715:)
711:(
705:)
701:(
695:)
691:(
685:)
662:)
658:(
639:)
635:(
629:)
625:(
619:)
615:(
609:)
605:(
599:)
595:(
589:)
585:(
579:)
575:(
569:)
565:(
559:)
555:(
549:)
545:(
539:)
535:(
529:)
525:(
519:)
511:(
505:)
501:(
461:e
454:t
447:v
383:.
353:.
324:.
296:.
267:.
245:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.