Difference between revisions of "Bug Tracking"

From Freephile Wiki
Jump to navigation Jump to search
(inital writeup)
 
 
Line 1: Line 1:
A quick [http://www.google.com/search?hl=en&client=firefox&rls=org.mozilla:en-US:unofficial&q=support+desk+tracking+bug+tracker+subversion+integrated&spell=1 Google Search] reveals many options for defect tracking systems.
+
Ten years after I first wrote up some notes on bug tracking, a lot has changed.  <ref>The old article can still be found [https://freephile.org/w/index.php?title=Bug_Tracking&oldid=2698 here].</ref>
  
The Opensourcetesting website (deserves it's own article on [[Quality Assurance]] with links to http://www.testmanagement.com/ ) offers a rather complete list of bug tracking databases: http://opensourcetesting.org/bugdb.php
+
Bugzilla and Request Tracker are still good choices today for bug / issue tracking despite being about 20 years old.  New options include simply using GitHub (makes sense if you're focused solely on the code) to [http://www.openatrium.com/ OpenAtrium] if you're about collaboration and Drupal.  [https://www.redmine.org/ RedMine] is a good system.
  
And Karl Fogel's book on [http://producingoss.com/html-chunk/ Producing OSS] (is undoubtedly a worthwhile read) has an appendix listing bug trackers http://producingoss.com/html-chunk/bug-trackers.html
+
I'm adding the infrastructure for customers to report issues and receive support.  Instead of launching an independent (or even hosted) application, I'm interested in using Drupal's Project Issue so that it naturally integrates with the {{CompanyName}} website (built on Drupal).  Or, possibly, using Phabricator as a service.  After trying [https://admin.phacility.com/ Phabricator], I'm really impressed.
  
[http://linas.org/linux/pm.html This page] is an editorial + review of many categories of FOSS software from Bug Tracking to Support Desk solutions (perhaps dated).
+
Either way, I'd like to initially start with
 +
# Company
 +
## Internal
 +
## Website
 +
## Wiki
 +
## QualityBox (already on GitHub)
 +
## Html2Wiki (already on phabricator at WMF)
 +
# Customer A
 +
# Customer B
 +
# Customer C
 +
# Customer D
 +
# Customer E
  
There are also many listings over at the [http://dmoz.org/Computers/Software/Configuration_Management/Bug_Tracking/ DMOZ page on Bug Tracking]
+
{{References}}
  
One of the old standby's of Bug Tracking is 'RT' or [http://www.bestpractical.com/rt/ Request Tracker].  By now, it's up to version 3.4.5
+
[[Category:Project Management]]
 
+
[[Category:Software]]
One PHP product is called '[http://workbench.sourceforge.net/ Workbench]'  Meanwhile, another is called [http://ruqueue.rutgers.edu/ RUQueue] (written at Rutger's University as a PHP version of RT)
+
[[Category:Development]]
 
 
More PHP options include the [http://www.horde.org/whups/ Whups] system from the Horde. and [http://kennwhite.sourceforge.net/codetrack/ CodeTrack] and [http://flyspray.rocks.cc/ FlySpray doesn't look too bad]
 
 
 
For Python, there is [http://roundup.sourceforge.net/doc-1.0/features.html Roundup] and also [http://www.issuetrackerproduct.com/ IssueTracker] which is built on Zope
 

Latest revision as of 21:57, 22 December 2016

Ten years after I first wrote up some notes on bug tracking, a lot has changed. [1]

Bugzilla and Request Tracker are still good choices today for bug / issue tracking despite being about 20 years old. New options include simply using GitHub (makes sense if you're focused solely on the code) to OpenAtrium if you're about collaboration and Drupal. RedMine is a good system.

I'm adding the infrastructure for customers to report issues and receive support. Instead of launching an independent (or even hosted) application, I'm interested in using Drupal's Project Issue so that it naturally integrates with the eQuality Technology website (built on Drupal). Or, possibly, using Phabricator as a service. After trying Phabricator, I'm really impressed.

Either way, I'd like to initially start with

  1. Company
    1. Internal
    2. Website
    3. Wiki
    4. QualityBox (already on GitHub)
    5. Html2Wiki (already on phabricator at WMF)
  2. Customer A
  3. Customer B
  4. Customer C
  5. Customer D
  6. Customer E

References[edit source]

  1. The old article can still be found here.