Similar to what Amazon has in their review system, I would like to see a way for people to review bug reports. Below the description of each bug report (or possibly even comment), there would be a "Was this information useful to you?" and a Yes/No link. Obviously this rating system would be integrated into the user accounts, so people with better statistics have 5 stars next to their name in bugzilla. The overall effect would be that people would try to be much clearer, informative and the amount of useless bug comments and bug reports would steadily decrease!
In this case, what would be very useful is a <select> close to the description (comment 0) allowing you to only show comments having at least x stars (x=0..5, with 0=all). Do we have another bug about the same thing, but based on your privs or your role relative to the product? say, dave with a big gold disk (project leader), myk ditto, mkanat a orange one (or pink or blue, ...) as release manager, etc... + reviewers + trusted guys for a given product (so it would be a per product thing). This would also help in trusting some comments/decision.
(In reply to comment #2) > with 0=all). Do we have another bug about the same thing, but based on your > privs or your role relative to the product? say, dave with a big gold disk > (project leader), myk ditto, mkanat a orange one (or pink or blue, ...) as > release manager, etc... + reviewers + trusted guys for a given product (so it > would be a per product thing). This would also help in trusting some > comments/decision. I think the best way to go for that would be a "comment_vote_weight" field in the profiles table, where certain people's "votes" or "karma" on comments would be weighted higher than other people's. It could be set by an admin or by somebody perhaps with "bz_grant_comment_weight" privs, or something like that.
I think the best way to get a useful value of people's importance in the project is actually to let people click "Was this people useful to you?". That way we can actually get an honest value of what people think. It will also reduce the amount of newbie-comments where people comment without looking at the previous comments (that is, newbies will heed before posting -- which might be a good learning experience).
Bug 136310 comment 7 wants more like "how was this comment useful to you". since this is the live bug, i do hereby deem it "comment-tagging".
From my perspective I see a lot more value in rating bug comments (bug#532474) than in rating an overall bug report. I think this depends on whether a particular Bugzilla setup is used as an issue tracking system mainly for developers to keep track of issues or whether it is used more like a support tool for end users to interface with the developers or technical support people. If the tool is mainly used by developers, QA, and technical support as it is in our company then rating comments makes sense. Bug reports however, are either useful or not useful and in generally this can be indicated with the INVALID vs. other available resolutions. If end users are in the system then it makes sense that they could somehow indicate how useful the information within a bug-report was to them. Maybe it helped them understand which version in which the issue was to be addressed or maybe it indicated that the issue would not be fixed. Both of which are examples of useful information. Two things to avoid with bug report level ratings: 1. Confusion between rating the usefulness of the information in the bug report and the level of satisfaction with the resolution of a particular bug. 2. Stale ratings that were given before a significant amount of information in the particular bug report has changed. See unlike comments, bug reports themselves are living documents that can change over time making it unfair to retain ratings given before the bug report has been augmented or further refined.
Yes, this is my request also. Please add i have this problem also button like sumo forums. Also please add scoring system to comments.
You need to log in before you can comment on or make changes to this bug.