Agitators Anonymous: Bug Tracking
Last year, I suggested that our project should use a bug-tracking system. As I saw it, we didn't have a good way of making note of bugs or feature requests that weren't yet urgent, but should still be dealt with at some point. At about the same time, Jay wanted a bug-tracking system so he could quantify the times a business group asked him to fix an issue that had already been fixed. Fortunately, somebody inside the company had set up a web site that offered Source Forge-style artifact tracking, so we just jumped onto that. It's been a big success for the project on several counts. Right now, though, we have a few too many open artifacts. Jay complained that we'd exceeded 50, which is the default number the system will display at a time. Could Josie and I close four of our bugs, thus bringing the count back to what would fit on one screen? Josie asked if it was possible to display more than 50. I responded with a screen shot of the how-many-to-display box showing 54. Jay chided that surely it was more efficient for Josie and I to close bugs than it was for him to type two characters. I responded, naturally, by submitting a new bug, the title of which was "Fix open bugs in ".