From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC Bugzilla interaction guide for devs & editbugs users
Date: Sat, 11 Sep 2010 07:17:01 +0000 (UTC) [thread overview]
Message-ID: <pan.2010.09.11.07.17.00@cox.net> (raw)
In-Reply-To: 20100910183238.11a96a69@epia.jer-c2.orkz.net
Jeroen Roovers posted on Fri, 10 Sep 2010 18:32:38 +0200 as excerpted:
> If the reason you propose this is visibility, then maybe we should make
> the quicksearch option include more than just open bugs. I've thought
> about having UPSTREAM/DUPLICATE/INVALID added so that bugzilla users can
> more easily discover whether a bug was already reported and was deemed
> fixed, a duplicate of another bug or canonically invalid.
I've wondered why quick-search didn't do ALL by default, myself.
Bugzilla's advanced search is quite difficult for users to get right (I
never seem to, tho it may be konqueror's scripting or some such, so I use
quick-search and either specify version or start from the bottom and work
backward as far as I believe reasonable), so I presume most use the quick
search nearly exclusively. That being the case, and further, the case
being that users almost certainly will want ALL, having that NOT the
default is simply begging for users to miss closed bugs.
So I'd say make ALL the default, and have an ONLYOPEN or some such option,
instead, to cover the current default for those who actually want/need it.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2010-09-11 7:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 8:32 [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users Robin H. Johnson
2010-09-06 8:39 ` Dirkjan Ochtman
2010-09-06 12:38 ` Alex Legler
2010-09-06 15:31 ` Michael Weber
2010-09-06 16:07 ` [gentoo-dev] " Christian Faulhammer
2010-09-06 21:24 ` Ryan Hill
2010-09-06 12:10 ` Christian Faulhammer
2010-09-06 12:36 ` Alex Legler
2010-09-07 20:47 ` [gentoo-dev] " Róbert Čerňanský
2010-09-07 21:30 ` Robin H. Johnson
2010-09-07 21:43 ` Andreas K. Huettel
2010-09-07 21:44 ` dev-random
2010-09-07 22:05 ` Pacho Ramos
2010-09-07 22:53 ` [gentoo-dev] " Duncan
2010-09-08 4:44 ` Ryan Hill
2010-09-10 16:32 ` [gentoo-dev] " Jeroen Roovers
2010-09-11 7:17 ` Duncan [this message]
2010-09-11 13:43 ` [gentoo-dev] " Jeroen Roovers
2010-09-11 21:58 ` [gentoo-dev] " Róbert Čerňanský
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2010.09.11.07.17.00@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox