Bugzilla feature requests

[Bjoern A. Zeeb]

On 27 Jul 2014, at 12:14 , Bjoern A. Zeeb <bz at freebsd.org> wrote:

> Hi,
> 
> (1) is there any way to show diffs “inline” somehow;  I really just want to browse them and not get them all into my downloads folder, have to open a terminal, have to use a pager, ..  this costs too much time.

Aha; so two problems:

(a) if you hover over the file.diff link on the left it says “View the content of the attachment” but that’s not what it means as it delivers it as:

	Content-Type: text/plain; name="file.diff"; charset=
	Content-disposition: attachment; filename=“f(b)ile.diff”

(b) the “diff” link on the right in the box is actually the “show diff in fancy web UI” link.

Would it be possible to change the hover of (a) to “Download diff” and the link description of (b) to “show diff”?   Yes I bet that’s upstream stuff, but if I have to use this thing and not just swear about it I’d rather have someone improve it’s usability


> 
> (2) upon editing a field in Bugzilla there is “no way back” without completely reloading the page:  e.g, Assigned-To:  if you click “edit”  the “take it” goes away and there is no way to click it anymore;  similar for Status, when you accidentally hit “mark as duplicate” right below the drop down you are screwed and have to start over;  this kills too much time.
> 
> (3) The committers guide should also state which login to use (either in the Kerb/LDAP) section or in the various web frontend sections;  I can never remember if I need the realm for FreeBSD.ORG or not and whether it’s case sensitive or not.  Too many places with too many different policies.
> 
> (4) does a set of command line utilities exist by now to search and edit bugs?  I was promised this on developers ages ago; long before we switched.
> 
> (5) I am totally confused by section 2 and 3 of https://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/article.html  3 seems to reflect the old gnats states; section 2 is a nice piece of fiction  but totally confusing.  Can someone please remove all the superfluous text, make sure that Joe doesn’t end up with the bug no matter what Jane thinks, and maybe draw a diagram?

(6) Changes to individual fields on the top do not always trigger emails;  can you please document which fields are tracked (revision history alike) and which do trigger emails, and which fields one can change 1000 times without anyone being notified?



— 
Bjoern A. Zeeb             "Come on. Learn, goddamn it.", WarGames, 1983