Hi * > Works fluent. > I find it hard to judge how much of an improvement it is, how much > easier it is to fill in.
I find that this is a vast improvement for the regular user. (This because I consider myself more or less a regular user.) Splitting up the process into segments makes the task of bug reporting a lot less daunting. I really like this idea, and I think it has been needed for a long time. Thanks to CPH for this work. Now if we could only get a simple search interface too. ;) > >From a QA volunteer's perspective, I think it would also be nice to have the user's initial reaction as to how important the bug is. That way the QA volunteer doesn't have to make that decision for everfy single new bug. We might not have the full 1-5 ranking (for example, we might reserve 1 for crashes), but we could still provide a priority scale. Perhaps it could be radio-button based. Something like: How high a priority do you feel fixing this bug should be? -Top priority (translates to a priority of 2) -Regular priority (translates to a priority of 3) -Lower priority (translates to a priority of 4) This is just an example, of course. Maybe someone else has a better wording or translation to the priority scale. Maybe we could also have a summary of the information included on the priority explanation page (http://qa.openoffice.org/scdocs/ddIssues_EnterModify.html#priority) so that the user has a good idea of what to put. Thoughts? Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
