PR-Tracker: Bug Tracking Software for Windows and the Web

PR-Tracker helps manage software development projects by tracking software bugs with problem reports. PR-Tracker records problem reports in a network database that supports simultaneous access by multiple users. Features classification, assignment, sorting, searching, reporting, access control, user permissions, attachments and email notification. Supports easy configuration of data collection and workflow on a project by project basis. Redundant data storage for speed and data corruption recovery.

PR-Tracker Web Client performs bug tracking over the internet or an intranet without using a browser. It has the same easy to use Windows interface and features of PR-Tracker and uses local caching to provide top performance without compromising features.  Use it to connect to a PR-Tracker database from remote locations or to collaborate with other companies. Included with PR-Tracker.

ProblemReport.asp enables people to enter problems reports with attachments into the PR-Tracker database using a browser. It's a great way to implement beta test bug reporting, customer support, or your company helpdesk. Free.

Each bug report represents hours -- maybe even days -- of work. It's important company data, which should be well protected and well organized. Bug reports should be recorded in a database that is backed up on a daily basis. A bug tracking system, such as PR-Tracker, should manage that database. Here are some guidelines for effective bug tracking.

1. Make a  build of the software daily
Bug tracking works best in an environment where there is a daily build. This enables testers to test the most recent version of software so that they aren't reporting bugs that have already been fixed. They are also discovering newly introduced bugs quicker while the code is still fresh in the mind of the developers that introduced them.

2. Use build numbers
When applicable, build numbers should be used to specify what version of software a bug was found in, what version it was fixed in, and what version a fix was verified in. Revision numbers of source code modules modified to fix bugs are helpful notes for developers, but they aren't necessary or sufficient to coordinate work between test and development. Use build numbers instead.

3. Use a process to handle bug reports
Bug reports should go through a process that ensures that they aren't closed if they shouldn't be. Such a process should require that the person who reported the bug be the one to verify that it has been fixed or to approve any other type of resolution. The typical bug report life cycle would include the following status values: New, Assigned, Resolved, Verified and Closed, respectively.

4. Use a resolution field
To keep the bug report life cycle simple, use a resolution field to specify how problems are resolved. Possible resolutions include: Fixed, Won't Fix, Not Reproducible, Duplicate, By Design and External.

5. Don't triage bug reports in meetings
Avoid using a committee or meeting to triage bug reports. This will use a lot of man-hours that could be used fixing bugs. If the schedule dictates a triage, don't close bug reports in the meeting because this will circumvent the quality process by sidestepping testers that report bugs. Instead, use the bug triage to reprioritize, postpone, or resolve as won't fix.

6. Handle feature requests separately
Feature requests and specifications are often recorded as bug reports. These should be recorded separately so that they can be triaged, and so that they don't skew statistics for measuring software quality.

7. Describe how to reproduce bugs
A bug report should include a step-by-step description on how to reproduce the bug. This reduces the amount of time developers spend trying to reproduce the bug before they fix it. Finding the minimal steps to reproduce the bug will save even more developer time.

8. Record how bugs are detected
Keeping records on how bugs are detected helps you determine how best to spend your testing dollars. Suggested choices for a detection method field include: Interactive Testing, Test Script Execution, Test Script Design, Unit Testing, Integration Testing, Code Review, Beta Testing and Customer Report.

9. Keep bug reporting simple
Don't make bug reporting complicated by requiring entry of more data than is really necessary. If it's too much work to enter bugs into the tracking system, some bugs won't be entered, or people may start going around the system and begin reporting bugs by email or word-of-mouth.

Customer Comments

PR-Tracker speaks for itself. It has all the practical functions of a professional bug tracking system, yet it is designed for usability. It is intuitive, simple, and straightforward. PR-Tracker is also highly affordable, it minimizes the overall cost by utilizing your existing hardware and software systems and integrating with them seamlessly.
-- Krishna Patel, Quality Assurance Lead, Chenoa Information Services

As a fellow software engineer it is very refreshing to purchase a product that actually works well, and is extremely reliable. In addition your user interface is probably the easiest I have ever used. The entire design, from installation, licensing, configuration, and use is extremely well designed, simple, and reliable. Kudos!
-- Mark Walsh, Senior Software Engineer, Tokyo Electron Arizona, Inc.

I just wanted to drop your company a note to let you know how much I LOVE PR-Tracker! I spent a good 4 hours on it yesterday after I received the codes to use it. I can't believe how easy it is to use. I've entered all of my cases in and now I am completely organized. I really like the way that I can edit the software to personalize fields. It has made my life SO much easier. Thanks a lot. This was exactly the type of software I was looking for!
--Tim Kelly, IT Manager, Santa Fe Collection

The simplicity of the user interface meant that training time was nearly nothing. I have been able to extend functionality within minutes of getting a new idea.
-- Kathy Deel, Senior Systems Analyst, Rapid Systems Solutions Inc.

We have been using PR-Tracker for some time now and found it to be a very useful, extensible tool. It is a great asset to our software development productivity! We have also found it to be quite stable and problem-free, a credit to your development team.
--Kevin P. Cross, Ph.D, Director of Software Development, LeadScope, Inc.

I have been developing software for over twenty years and know first hand the value of problem tracking. My company has built a couple of custom problem tracking systems in the past. I like your solution better than both ones that my company built. Both my applications were small budget projects, in my fairness, however I don't believe in re-inventing the wheel and will continue to use your product, since there is no better value on the market.
--John Galvina, Glavina & Associates, Inc.

The members of my team love your product! Some of their comments: Whoever designed this has had to actually use this kind of application in the real world -- they know exactly what we need it to do and they've made it very simple and easy to use : Everything I've thought of so far I'd like this program to do, I've found that it does--and it's easy to find and use the function I'm thinking of.
--Anita Kay, User Analyst, Kaiser Permanente