[katello-devel] [katello-internal] Please Read: Bugzilla Best Practices

[Jeff Weiss]

On Thu, 2012-03-01 at 16:57 -0500, Bryan Kearney wrote:
> On 03/01/2012 04:55 PM, Jason Rist wrote:
> > Hey Everyone -
> > 	Sorry to be the nag, but I have a few nits to pick.
> >
> > When creating bugs, can you please in the bug summary state the following:
> >
> > 1.) "This is for the UI"  || "This is for the CLI" - it's somewhat
> > unclear when reading the bugs, and if you state that it makes it so much
> > easier to parse the problem.
> >
> > (Side note on that, I could have sworn that we selected components when
> > reporting, where is that on the bz itself?)
> >
> > 2.) Can you please specify the browser you're using if it is for the UI?
> >   We should at the very least support 3.6, so if you're having problems
> > with something, please state whether you tried it in 3.6.  (Usually if
> > it works in 3.6, it works elsewehre. Not always, though.)
> >
> > 3.) If you have a stack trace or javascript console errors, please
> > attach them as txt, please do not paste them into the bug.
> >
> > (Yes, I know I'm guilty of this, but have changed my ways!)
> >
> > Thank you so much!
> > -Jason
> >
> 
> Also, adding the tar ball from /usr/share/katello/script/katello-debug 
> would be helpful.
> 
> -- bk
> 
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel

+1 on fixing components rather than trying to abuse the summary line.

I'd like a script that we can run right on the server that takes
summary/component/description and just grabs the version and logs right
from the installation, and creates the bug via bz's api.

I've been meaning to write one, haven't had time yet.  Post V1
hopefully.