UI module owner

[Dennis Melentyev]

В пн, 26/06/2006 в 18:06 +0100, Gervase Markham пишет:
> Dennis Melentyev wrote:
> > Well, it's mostly role-dependent. What about putting some role
> > schemes/UI/WorkFlow/etc in?
> 
> Now we're thinking along the right lines :-)
:)

> >> Why is basic search "too minimalistic"? And for whom? I assume you don't
> >> mean "because it doesn't have enough widgets"; so do you mean "because
> >> it doesn't find what you want some of the time"?
> > It's more like "I'd like to specify also Open/closed flag, user and some
> > date-related stuff".
> 
> You can specify an open/closed flag on the basic search.
Well, missed that, anyway I go directly to Advanced one. :)

> Date-related stuff seems to me to be well into the realm of advanced
> queries. After all, you can get simple date-related stuff for filing
> date just by searching by bug number. And, assuming we fix up the
> sorting on the results page, you could sort by last-changed-date to get
> recently-changed bugs too.
I personally hate remembering the numbers. Also, having lot's of bugs
it's really hard to keep them all in mind.

> > Yes, of cause it's doable via AdvSearch page. But each time you open it,
> > you have to re-read it twice or so to remember what all that controls
> > do.
> 
> Are the labels not clear enough that one reading is enough? :-)
There are tooo much labels to read them all. I have to pay attention to
each of them to find one I really need.
While looking at the page one would need to see the blocks first, then
go to these blocks and look for something particular. Currently,
AdvSearch page does not split good enough. <HR> is not enough, help link
is hardly visible along the other controls.
Eyes needs "anchors" to stop at. Then you could easily narrow your task.

> > Good alternative would be expandable panels like in show_bug with button
> > mentioned already here.
> 
> I do think expandable panels is worth looking at on that page. But we
> would need to study people's queries to see which fields to group onto
> particular panels.
> 
> >>>> - Is that page supposed to be used by newbies?
> >>> No. But they do often need somewhat advanced, but not over-helming
> >>> pages.
> >> What evidence do you have that people who have graduated from the simple
> >> search form (and therefore already have some familiarity with Bugzilla)
> >> still find the complicated one hard to understand?
> > It has too many controls and no place to concentrate the sight at.
> > Current layout offer more details moving from <hr> to <hr>, with
> > main/primary controls at the top of the page.
> > The biggest problem is: one have to pay too much attention. (And,
> > better, need internals understanding to some degree)
> 
> Which parts need understanding of internals? How would you change them
> to not require such understanding?
Well, I'm still not sure how to specify e-mail patterns in different
fields/pages (review req, search page, groups administrating). There are
regexps and simple patterns. Actually I often grep the code as it is
just faster then find a document.

> (Boolean charts require some internals understanding, but I think that's
> OK, because you couldn't have them stay that powerful if you removed
> that requirement.)
Well, semi-agree.

> >>> Another user role is "Customer The Great" often under-qualified to
> >>> fill-out all controls, not patient and not willing to learn this "ugly
> >>> pages". But their reports are gold for us.
> >> Why are you pointing your customers at the advanced search page? What do
> >> you expect them to accomplish there?
> > They are working with us on bugs related to their products/components.
> 
> But don't you use groups to make sure that bugs in their
> products/components are the only ones they can see anyway?
Yes. Sure! But there are still more then one item available for them.

> > Yes, but adapting workflow to corporate standards should be much easier
> > than it is now.
> 
> I agree with that. Evidence from the newsgroup suggests that customising
> the workflow (statuses and resolutions) is an extremely common request,
> and currently to do it I believe you have to hack Bugzilla in a way
> which makes it hard to upgrade.
Yup! The most annoying thing about Bugzilla.

PS. My previous post died somewhere in list-processor bubbling about
header longer than 4 hundred and a drop. Pity, but I not fond of trying
to re-post it...