<br><br><div class="gmail_quote">2009/5/7 Austin English <span dir="ltr"><<a href="mailto:austinenglish@gmail.com">austinenglish@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2009/5/3 Nicklas Börjesson <<a href="mailto:Nicklas.Borjesson@ws.se">Nicklas.Borjesson@ws.se</a>>:<br>
<div class="im">> Explained to me?? ...this is just incredible.<br>
> Regardless of what I have said, you have repeated almost the same things,<br>
> it's like you haven't been reading my posts!<br>
><br>
> Leave me alone, I want to talk to someone else.<br>
<br>
</div>No offense, but you should probably take the lack of (repeated)<br>
responses as a sign.<br>
<br>
You've been answered several times by several people, and the answer<br>
has been (mostly) the same.<br>
<br>
Bugzilla is a developer's tool, with bugs reported by users. Severity<br>
levels are there for how they affect Wine *overall*, not the user<br>
experience. Such things belong in the AppDB/etc., not bugzilla.</blockquote><div><br></div><div>Having it in a field in bugzilla with a list of options is potentially a lot better than expecting users to enter the information in the description without being prompted. I'd suggest:</div>
<div><br></div><div>Application can't start.</div><div>(default) Something I need to do is broken, but enough of the app still works to be useful for other tasks (e.g. a word processor with broken equation editor).</div>
<div>The app is totally useless (e.g. a word processor with broken Open & Save dialogs).</div><div>Part of the app is broken but I can work around the problems.</div><div><br></div><div>along with instructions to file installer bugs under "Installer for XYZ" because installers have the same potential for partial breakage (can't select install directory vs shows negative free space and refuses to install at all)</div>
<div><br></div><div>This was already suggested, but the options addressed multiple orthogonal issues (how usable is the app vs what kind of breakage) which someone pointed out would be even more confusing. Keep the what broke in the description where users will naturally report it, and provide only an impact (hey that might not be a bad name for the field -- "impact") level in a new dropdown list.</div>
<div> </div></div>