[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#33133: Suggestion to make bugs.kde.org easier to use
From:       richard () krogoth ! dyndns ! org
Date:       2001-09-30 18:31:57
[Download RAW message or body]

Package: bugs.kde.org
Version: KDE 2.2.1 
Severity: wishlist
Installed from:    Mandrake RPMs
Compiler:          Not Specified
OS:                Not Specified
OS/Compiler notes: Not Specified

I have a suggestion that could make the bug reporting tool easier to use: one of the \
hardest things to do when reporting a bug is to search for previous reports, so it \
would be useful if there was a simple classification system. For example, the user \
could select their application and version, select the problem (something isn't \
happening, something shouldn't be happening, something is displayed wrong) and then \
specify their general area where it's not working (main window, flash plugin, etc), \
and then select a more specific area. So to report that konqueror isn't starting, I \
would select Konqueror, 2.2.1, something isn't happening, main window, not opening. \
By splitting this into several different selection boxes, it should be possible to \
avoid bugzilla-type 5000 item lists - after each selection is made, another list \
would pop up if JavaScript is enabled or the page would reload with the new list \
(after the user clicks on "continue") if not. This way people could easily narrow \
down the number of previous bugs they're searching (the number of reasons the latest \
Konqueror wouldn't  display the main window should be small) and categorize their \
report so other people with the same problem would find it faster.

(Submitted via bugs.kde.org)


[prev in list] [next in list] [prev in thread] [next in thread]