I have encountered this type of feedback report evaluation where the evaluation simply does not make sense similar to what you saw. The thing to do is send an email to customer support explaining the situation and that this feedback report needs to be reevaluated. Obviously a hard crash is a bug and they need to fix it.
I can see two possible explanations for this evaluation. 1) The evaluator entered the "not a bug" mistakenly against your report and meant to do that against a different report. If that is the case, then cut them some slack. 2) The evaluator is whacked out, on drugs, or more likely "inexperienced." This is a management problem upon RS's part since they don't want such critical bugs to slip through because of the incompetence of a single employee. If the employee did this on purpose knowing full well what they were doing, then retraining is required. Let RS figure out the circumstances of why the evaluator marked it as a bug. If customer support comes back saying it still is not a bug, then you have the right to be steaming. Bringing this matter to the attention of the manager of the evaluator will motivate that evaluator to be more careful in their future evaluations. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
