Open main menu

Bug Tracking

Revision as of 21:57, 22 December 2016 by Freephile (talk | contribs)

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)

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

  1. The old article can still be found here.