UI module owner
Dennis Melentyev
dennis.melentyev at infopulse.com.ua
Sun Jun 25 10:39:57 UTC 2006
В пт, 23/06/2006 в 20:28 +0100, Gervase Markham пишет:
[...]
> Also, for the ease-of-use goal:
> do we have any more specific data than
> "people complain Bugzilla is hard to use"?
Well... Trying to put some more specific data, I'd say:
Bugzilla UI (Search page at the first place followed closely by bug
entry page) are way too overloaded with controls and lots of them are
not intuitive.
It's getting intuitive when you getting more and more familiar with
Bugzilla process, but is a complete mess for a newbie.
IMO the best idea is to have a wizard-like search and bug entry pages,
with ability to switch back to current pages when "the wizard" will
start abuse you.
> Is the entire UI so poor that
> a complete redesign is required?
There are also some design/style issues. It doesn't looks
sexy/serious/cool/whatever word you know for a big, well-known and full
featured application. It looks like knee-knitted helper thingy. This
doesn't mean any functionality is missed. It just does not impress from
the very first look :)
> Or would we be better off finding the
> tasks that people find hardest, and incrementally improving the UI in
> those areas towards a defined goal?
As for the previous issue, I think out there should be a lot of young
and clever web-designers who would be able to create a couple of good
skins while on summer vacation.
Yet another idea is to have several default (pre-shipped?) skins
selectable by USER in his profile:
1. Just current (classic) skin
2. Sexy-dumb-n-bullet-proof-wizardry (anyway, we definitely need one for
collecting bug reports from customers, who could not always be smart!)
3. wap-enabled minimalistic
4. special skin for disabled people
All this skins should have some requirements, like #2 require
CSS/JavaScript/other modern features while #1 should be lynx-friendly.
We do have all inder the hood to do that, just missed this idea for
Google Summer of Code. :)
> (The answer to these things may be yes; but they are questions we need
> to ask.)
100% agree.
More information about the developers
mailing list