|
|
Home | Switchboard | Unix Administration | Red Hat | TCP/IP Networks | Neoliberalism | Toxic Managers |
| (slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix | |||||||
| News | Recommended Books | Recommended Links | Perl Wiki as System Administrator Tool | Perl Blog Engines |
| Bugzilla | Trac | Version Control & Configuration Management Tools | SE quotes | Etc |
|
|
Bug tracking systems (BTS) are simple tools for a very complex problem - tracking and managing defects, bugs, issues and problems. Companies that use a good BTS suitable for the problems in hand can get substantial improvements in productivity. BTS gives you the ability to assign categories to bugs, and then analyze them according to those categories. Previously and even today for small organization Bug tracking system also doubles as a custom based knowledge system, but lately this role was delegated to Wikies.
For example Trac (written in Python) positions itself as both bug tracking system and wiki:
Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.
It provides an interface to Subversion and Git (or other version control systems), an integrated Wiki and convenient reporting facilities.
Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all current and past project events in order, making the acquisition of an overview of the project and tracking progress very easy. The roadmap shows the road ahead, listing the upcoming milestones.
If you are involved in something very complex there is a lot of value in using a simple tool. It is simpler to learn, simpler to use and simpler to do what it is you need to do. Complex tools that try to integrate with other areas of the project's management carry a much higher overhead in learning, using and doing. Often complex tools are left on the shelf and paper-based systems used by the teams doing the work.
Bug tracking tools provide a means of consolidating a key element of project information in one place. When a bug is found, a tester or quality analyst records the bug and the steps needed to reproduce it. A developer will then fix it and tell the tester it has been fixed. The tester will then check the bug has really been fixed, and close it. Project managers can then see which bugs have been fixed, which are outstanding and how long it is taking to fix defects. Senior management can use reports to understand the state of the development process.
|
|
For any but the simplest projects, it is hard to keep track of what bugs have been detected, and which of them have been fixed. As well as automating this process, bug tracking tools make possible to produce some metrics and reports which, if not overdone, can be useful.
Because you have an instantly available database of bugs you can take steps that help to lessen their number. Even a simple summary reports showing how many show stopper bugs are still unfixed in your software, or how long it is taking on average to fix high priority bugs have a great value.
Reduced clerical overhead is another benefit.
Because there are so many bug-tracking and ticketing systems, I've split the list into two: Open Source and Commercial. Note some important gray areas between the open source and commercial packages: some of the open source packages are commercially supported and widely used; whereas some of the commercial packages have small customer bases and are barely supported. Some of the commercial packages, e.g. Keystone, makes broad use of open source technologies for its implementation, and is *almost* open source (whatever that means). Some of the commercial packages make source code available at a very modest price.
It provides an interface to Subversion and Git (or other version control systems), an integrated Wiki and convenient reporting facilities.
Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all current and past project events in order, making the acquisition of an overview of the project and tracking progress very easy. The roadmap shows the road ahead, listing the upcoming milestones. �
Do not confuse with the GNU GNAT tool, the GNU Ada95 Translator.
Features:
Features:
The web interface will sorely disappoint web users used to web-based bug tracking tools. The web display does not use HTML tables for layout, and thus the pages look very raw. E-mail headers on the bug submissions are not trimmed, and thus most of the web page is filled with with cryptic-looking, dense, and not very important email headers. There is no way to manipulate reports from the web interface. Most customization, as to projects, sub-projects and states has to be done by hand by editing configuration files. There is no support for user authenticati/sourceforge.net/projects/phpsat/">PHPSAT PHP System Administrator's Tool. Its an issue tracker.
The Anthill Bug Manager is a tool that aids code development by keeping track of bugs in a medium-sized coding environment. It accomplishes this with a clean, simple, and fast interface that contains the essential features, but avoids the complexity associated with similar tools. It is written in Perl, requires an SQL database as a backend, and is Web server independent.
Scmbug is a system that integrates software configuration management (SCM) with bug-tracking. It aims to be a universal tool that will glue any source code version control system (such as CVS, Subversion, and Arch) with any bug-tracking system (such as Bugzilla and Mantis).
Bug Traction is a Web-based bug tracking system written in Perl with DBI. It is based on Bugtrack, but adds a number of features. It should work in all situations where Bugtrack works, but there are features that have been added (such as attachments) that may not yet work with any database backend other than MySQL. In all other respects, Bug Traction is true to the Bugtrack heritage which it shares and should work on a variety of platforms and with a variety of database backends.
OTRS (Open Ticket Request System) is an open source Ticket Request System and email management system with many features to manage customer telephone calls and email. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. It is useful for people who receive many emails and want to answer them with a team of agents. It has been tested on Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x, and Windows.
OTRS is an Open source Ticket Request System (also well known as trouble ticket system) with many features to manage customer telephone calls and e-mails. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. Do you receive many e-mails and want to answer them with a team of agents? You're going to love the OTRS!
It is distributed under the GNU General Public License (GPL) and tested on Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x and Windows.
The ((otrs)) company provides commercial services (e.g. support, consulting, pre-build-systems, etc.) for the OTRS (English and German).
Try our demo system to get an impression of this kind of magic.
To install PerlDesk you need the following software on your computer:
Perl (www.perl.com / www.activestate.com)
MySQL (www.mysql.com)
Web Server e.g. Apache
Perl Modules (www.cpan.org)
DBI / DBD::MySQL
Digest::MD5
PerlDesk Features / Overview
Using PerlDesk in your organization will make your user emails/support requests easy to track and manage, it allows staff members to be assigned to single or multiple departments saving time assigning user requests.
PerlDesk makes submitting tickets easy for users, by allowing two methods:
Direct Email Submission
Users can send email to your company which will be logged, assigned to a specific department and given a tracking number. You can setup multiple incoming email addresses allowing you to completely manage user communications.
Web Based Submission
Included in PerlDesk is a web based client area and submission form, where users can login and track/submit any support requests easily.
Client Area Features
The web based user area can optionally be used as a resource for users to submit and track help desk submissions and emails. An overview of the features:
Multiple Language Support
Quick User Signup
File Attachments from web based form
Ability to assign a priority for the request
View support request histor
Submission Tracking without logging in (via submission key)
Unlimited number of users.
Flood Prevention for incoming emails, this only allows a user to submit a request every x seconds.
Searchable Knowledge Base (managed by staff members)
Staff Area Features
An additional section of PerlDesk is the staff area, this is where you can allow staff members to login and respond to user requests.
Performance Tracking, staff members can view the % of calls they have closed
Rating Performance, users can rate how helpful a staff member was allowing satisfaction reporting in the administration
Private Staff notes can be set on help desk requests, so that users cannot view them
Assign requests to other departments or staff members
Staff Members can view/attach files when responding to user requests.
Easy call display, showing Emergency, new and open requests
Predefined response templates
Knowledge Base management
Ticket notifications
Many, many more features
Administration Area Features
The administration is where you can control all users/bills and the system setup. Some of the main features of the admin area are:
Change layout via the template editor
User Management, including the ability to create user accounts
Manage Staff, view staff members performance and response time
Ticket Overview
Create an unlimited number of support categories
Ban email addresses (bannin an email address will remove its ability to email submissions)
Manage software configuration, many options.
E-mail All Users
E-mail All Staff Members
Search Customers
View online/active staff members
Customize the whole design via the templates very easily
Edit the email response templates
# re: Bug Tracking We use Mantis, which has proved so far to be perfect. Feature rich, stable, simple, quick & easily customizable. Not to mention multiplatform.Posted @ 9/22/2004 8:26 AM
# re: Bug Tracking I like Gemini by www.countersoft.com. Free license for up to 10 users.
Posted @ 9/22/2004 8:33 AM
# re: Bug Tracking I also looked at mantis, but there were a couple of very severe security issues in the past months. Internally we now use a simple howm grown app.Posted @ 9/22/2004 8:49 AM
# re: Bug Tracking <a href="http://www.axosoft.com/products/">Axosoft OnTime</a> is written for .NET Framework. Though, after more than a year of trading it is still quite raw to my sight.Posted @ 9/22/2004 8:50 AM
# re: Bug Tracking We're using a highly customized version of the asp.net startker kit. Some important added features are Sourcegear vault integration (similar to FugBugz), and user acceptance testing process. Any of course, it's all in C#. I will be releasing an open source version of this in the near future as well (nDevTracker).
Check it out here:
http://www.asp.net/Default.aspx?tabindex=8&tabid=47
and join in the discussion on the forums.Posted @ 9/22/2004 9:26 AM
# re: Bug Tracking I've use Mantis for my group, but I'd much rather be using Bugzilla.Posted @ 9/22/2004 12:27 PM
# re: Bug Tracking We use Bugzilla running on a Windows XP dev box (Apache / MySQL). We have a small team so this fits perfectly.
Our criteria for selecting a bug tracking solution:
* Easy to set up
* Free (as the decision to use bug-tracking software was made by the devs, not management)
Posted @ 9/22/2004 12:28 PM
# re: Bug Tracking We use Merant Tracker (Dev Staff) and FogBugz (Web Staff).
Merant is used because it's very flexible to how we want to prepare our bug reports.
FogBugz is used because it's cheaper and the Webstaff wanted something much simpler.
Hopefully VSTS will be our saviour and combine all this with a usable source control system.Posted @ 9/22/2004 3:54 PM
# New Team System Stuff - 2004-09-22Posted @ 9/23/2004 4:15 AM
# re: Bug Tracking Were using Agility and have been quite happy with it. Its highly customizable and has some great features.Posted @ 9/29/2004 3:11 PM
# re: Bug Tracking http://www.countersoft.com
Offers .NET but issue tracking system.
Using it for a while: simple and effective.
Posted @ 9/30/2004 6:44 AM
# re: Bug Tracking We also use Agility (http://www.agileedge.com) to track the bugs in our survey software.Posted @ 9/30/2004 6:28 PM
Google matched content |
Legacy:
mozilla.org Bugzilla -- the Mozilla bug database
WebCall (New Listing!)Bugzilla is open source software. Its source code has been released under the Mozilla Public License. Check out the Bugzilla project page if you would like to use the Bugzilla source to create a bug system for your own project.
WebCall is a web-based trouble ticketing system. It distinguishes itself from many other systems by including reports and graphs, such as a bar chart of tickets opened by month, or a pie chart of calls by customer. Can export to spreadsheets (excel format). The technology is Perl5 cgi-bin's backed onto the MySQL database. GPL'ed.
BATTS (Barnhard Associates Trouble Ticketing System) is a lean, elegant trouble ticket system with both command line and Web interfaces, written in Perl. It uses MySQL for its backend, and has a ticket-via-email interface for submission and informational logging. Features include support for tickets pending on or resolved when other tickets are disposed of, an ability to assign tickets to a person, an ability to categorize and prioritize tickets, and associating billing codes with various logging events.
Request Tracker Perl-based
RT is an industrial-grade trouble ticketing system. It lets a group of people intelligently and efficiently manage requests submitted by a community of users. RT is used by systems administrators, customer support staffs, NOCs, developers, and even marketing departments to track issues, outages, bugs, requests, and all kinds of other things at thousands of sites around the world.
OTRS Perl-based
OTRS (Open Ticket Request System) is an open source Ticket Request System and email management system with many features to manage customer telephone calls and email. The system is built to allow your support, sales, pre-sales, billing, internal IT, helpdesk, etc. department to react quickly to inbound inquiries. It is useful for people who receive many emails and want to answer them with a team of agents. It has been tested on Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x, and Windows.
The Debian bug tracking system is a set of scripts which maintain a database of problem reports.
Key features:
- All input and manipulation of reports is done by email; developers do not need on-line web access or accounts on the host system.
- Outstanding, recently closed and other listings of reports are made available via a webserver, and by an email request bot.
- Each report has a separate email address for submission of additional information.
- WWW listings of bugs can be mirrored by email or HTTP.
- Core functions do not require CGI scripts.
- The Debian Project's instance has handled 16000 reports over the past 3-4 years, and currently has a database of 5000 reports totalling 90Mb (January 1997).
- GPL'd.
The scripts have been parameterised so that they can be used for other projects besides Debian; however, for a feel of what the results are like please see my local mirror of the Debian Project bug database, which also contains the system's user documentation.
The system runs on Unix and expects to have its own (possibly `virtual') mail domain, with the MTA for the host system being configured to pass mail for the bug system to it via a pipe command. You will need a fairly complete modern Unix installation to use it; most of the code is written in Perl5. A full list of requirements is in the README.
| JitterBug 1.6.1 |
| JitterBug is a web based bug tracking tool. It was originally written to help the Samba
Team manage the huge volume of bug reports and queries they receive but is now also used by
a number of other projects.
This release features much better handling of SMTP errors in the internal mailer. |
Software Project Survival Guide - review
Cyclic System Administration Page
Static Source Code Analysis Tools (Lint) - CC++ Net Links
Software Composition Group Archive
Noweb home page -- Without wanting to be elitist, the thing that will prevent literate programming from becoming a mainstream method is that it requires thought and discipline. The mainstream is established by people who want fast results while using roughly the same methods that everyone else seems to be using, and literate programming is never going to have that kind of appeal. This doesn't take away from its usefulness as an approach.
Literate Programming and FunnelWeb
Bibliography on literate programming
ajh's literate programming page
TeX Frequently Asked Questions - Section 8
Patterns and Software Essential Concepts and Terminology
FBenchmarks -- Fact, Fiction, or Fantasy?
Non-Software Examples of Software Design Patterns
Addison Wesley Longman - Design Patterns for Object-Oriented Software Development
What are disign pattern
Standard method/class combinations
Use mandatory type signatures
+ naming conventions
Good documentation for humans
And can be recognized by tools
Implementing Design Patterns in Java
Doug Lea's Workstation -- very good list of references. Tell much about the author
Books On-line Call Numbers Starting With QA -- just great
Please Read This Page Carefully.... -- que electronic books online
Society
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
Quotes
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
Classic books:
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater�s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright � 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|
|
You can use PayPal to to buy a cup of coffee for authors of this site |
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.
Last modified: March, 12, 2019
