Difference between revisions of "Bug Tracking"
(inital writeup) |
|||
Line 1: | Line 1: | ||
− | + | 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> | |
− | + | 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. | |
− | + | 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. | |
− | + | 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 | ||
− | + | {{References}} | |
− | + | [[Category:Project Management]] | |
− | + | [[Category:Software]] | |
− | + | [[Category:Development]] | |
− | |||
− | |||
− | |||
− |
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
- Company
- Internal
- Website
- Wiki
- QualityBox (already on GitHub)
- Html2Wiki (already on phabricator at WMF)
- Customer A
- Customer B
- Customer C
- Customer D
- Customer E