Over the years we have had many different systems for gathering bug reports and feature requests. We used to have a system that was pretty transparent. You could search it, contribute additional information to a particular issue, etc. We could get a sense of how important a case was based on the number of you that added that case to your watch list. This system was very specific to your needs, which are the needs of a software developer. As a result, this system was created in-house.
A few years ago, an argument was put forth internally here at REAL Software that we shouldn’t be re-inventing the wheel by building and continuing to maintain our own, custom bug database system but instead should use one of the commercially available systems. There was a lot of sense in this argument. These systems had features that our system did not and they were maintained by others allowing us to focus on what we do best. But these systems were not without their downsides. The theory behind FogBugz, the system we use today, is to make the system of entering a bug as simple as possible for the end user because if you ask too much, users won’t provide feedback. The other assumption is that most users don’t need to search through your bug database. These assumptions are all quite reasonable for 95% of software users. It became obvious to us late last year that you, our customers, are not in that 95%. You are like us. You are software developers. You understand the importance of providing lots of detailed information. You want to search our bug database to see if a report has been filed before and see if a workaround exists. You will tell us which cases are more important than others.
With this in mind, we decided early this year that we needed a new Feedback system. FogBugz is fine for most software companies whose customers are not software developers, but it’s not ideal for customers who are. However, if you are looking for a feedback system for your product, I would certainly recommend it. We spent some time looking at what was good and bad about our old system and what was good and bad about FogBugz. We then set out to build a new Feedback system that would give you and us the best of both systems.
While the old system was designed to be opaque, the new system is almost totally transparent. You can search, and the searching is actually very cool. It’s simple and yet very powerful. It also includes relevancy information to help you track down the case that is the most likely match. You can filter reports by product, version, status and more. You can keep a list of your favorite cases to make it easy to keep track of them. You can contribute to existing reports, adding workarounds, example projects, etc. that others can use. If there is information that should be for our eyes only, you can mark the information you add as private. And last but most certainly not least, you can put your most important cases in order of your personal priority. This and the priorities of others are put together to create a score. This allows us to see what the most important cases (both bugs and feature requests) are. You will be able to see them too because the new Feedback system will show you the top 20 cases by score. We have added this because we want you to see that we are making an effort to address the most important cases first. That’s not always possible of course and some bugs get addressed as soon as they come in because they are very easy to fix and an engineer might be working on that part of the code when the bug is reported.
In the past, the score of a case was essentially the number of people that added that case to their watch list. Anyone could add any number of cases to their watch list to increase the priority. The problem with this is that it didn’t give us a true picture of what your priorities are. In the new Feedback system the only cases that are scored are those that are within the top 5 open cases on your personal priority list. The new Feedback system makes it easy for you to reorder your cases so that we can see your personal priority. Also, in the case of REALbasic, the edition of REALbasic you are using affects the score your top 5 open cases receive. Professional Edition users are given 3 times the priority of Personal Edition users. REAL Studio Edition users are given 10 times the priority. We are doing this because the more you invest in us, the higher we feel your priority should be. That doesn’t mean that a Studio user would always get higher priority. For example, if fifteen Personal Edition users put a particular case at the top of their list, that would have a higher score than a case at the top of a single REAL Studio Edition user’s priority list. This scoring system will help us understand which cases should be addressed to have the maximum impact on you, our customers.
When we have changed systems in the past, we have asked you to go through your cases and help us move them over to the new system. For some of you, this was a lot of work. We will not be asking that of you this time. We have automated the process of moving the cases over. However, we will need you to do one thing. Because you can’t search our current Feedback system, it is implied that all cases are private in that others outside of REAL Software can’t view them. We would not want to accidentally expose to everyone a case you thought was private. As a result, you will need to tell us (via a web page) which of your reports should be private and which should be public.
This new Feedback system runs on Mac OS X, Windows and Linux and will ship soon with REALbasic 2009 R4. It’s going to help us better serve you and it’s going to better allow you to help each other - whether it’s providing a workaround for a bug, or discussing the pros and cons of a particular feature. We look forward to your comments and suggestions.
Use the following links to view larger versions of the screenshots: