To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65006 Issue #:|65006 Summary:|The issue management is faulty (votes, disposition, |etc) Component:|www Version:|OOo 2.0 Platform:|All URL:| OS/Version:|All Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|openoffice.org IssueTracker Assigned to:|[EMAIL PROTECTED] Reported by:|raindrops
------- Additional comments from [EMAIL PROTECTED] Tue May 2 08:14:38 -0700 2006 ------- It would be safe to assume that issues get higher priority based on the following- (a) Impact on the product (OOo). (b) Number of votes given by users. (c) "first-come-first-served" basis (i.e., older issues taken up first). (d) Defects would be taken up before enhancements. This issue will explain how this principle is defeated because of faulty management of the issuetracker. Different aspects are discussed in this single issue for continuity's sake. If you want, I will split them into separate issues. 1. Faulty tallying of votes: Issues are supposed to be prioritized by the number of votes they get. But the thanks to a faulty management of the issue tracker, votes are not collected properly, as explained below: Many issues are found to be duplicate of other issues and closed. Some are copied into other issues and then closed. In many of such cases, the closure is done a long time after initialization. In the meantime, the issue attracts a lot of votes. When the issue is closed, however, these votes are not transferred to the other issue. Once a visitor votes for an issue, he wouldn't keep a watch on it, and if that issue is copied into a new one (or closed as a duplicate), he is not likely to transfer his vote to the new issue. IssueZilla certainly does not do this automatically. Let me illustrate this with an example: Issue 2977 had 59 votes. Issue 33851 has only 37. So, assuming that these votes are mutually exclusive, issue 33851 should have 59+37=96 votes as on today; making this one of the top-ranking issue. Against that, we have a paltry 37 votes there! So, when copying an age-old issue into a new one, we spoil its ranking by splitting the votes. 2. Loss of age-weightage: In some cases, issues are combined into a new issue. All the older issues are closed. This is a dangerous practice because the problem appears to be freshly raised. Also, the original "observed in-" information is reoplaced in a recent version. In our example, issue 2977 is >4 years, but the transformed issue appears only 9 months old! So, all other things being equal, issues older than that will now have their turn ahead of this one! 3. Enhancement vs defect: The issue handlers classify a problem as enhancement as "defect" only if OOo does NOT "work as designed". Compare that with some internationally recognized standards: >> www.isixsigma.com defines a "defect" as (a) Any type of undesired result is a defect, or (b) A failure to meet one of the acceptance criteria of your customers. >> ISO 9000 defines a defect as "nonfulfilment of a need for a stated or intended use". Further, it defines that this need can be stated or implied. The problem with such classification is that the urgency to tackle the problem is lost when it is identified as an enhancement. There are many issues where the user may lose data, yet it is identified as an enhancement. An example is Issue 2977 or Issue 33851, where a defective behavior can overrite data; resulting in unforeseen changes in the spreadsheet. This issue is treated as an "enhancement". Another example is when the behavior is not defined under some circumstances. Such issues are classified as "enhancement" even if the user stands to lose data! --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
