I see in the mailing list that some problem arise with bugzilla. myself, I'm often blocked by not knowing how to answer a question. So I think bugzilla screens should be split vertically like Yast screens are, with a help part. What kind of bug for what kind of component, for example. and with a default option. It's probably better to have a bug qualified "default" than qualified in a wrong category. When somebody wants to give several attachments and a comment, it's not obvious how to do this. It seems that if you fill a comment then go to attachments, the comment is lost after "need info", the reassignment should be made much more visible, I forgot it all the time :-( jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
Hello, Am Samstag, 22. April 2006 17:06 schrieb jdd:
So I think bugzilla screens should be split vertically like Yast screens are, with a help part.
Please don't - my screen is already to narrow to display search results (1400x1050 laptop display!). Please don't add an additional column. If in doubt, read http://en.opensuse.org/Submit_a_Bug and http://en.opensuse.org/Bug_Reporting_FAQ If your question is still unanswered, maybe one of those should be extended ;-) BTW: Maybe the section about YaST and Kernel bugs should be moved to separate pages (Bugs:YaST and Bugs:Kernel)...
What kind of bug for what kind of component, for example. and with a default option. It's probably better to have a bug qualified "default" than qualified in a wrong category.
I guess this isn't a really problem - worst case is a "this is no bug in $component - reassigning to ..." comment. Simply use the component that looks best to you ;-)
When somebody wants to give several attachments and a comment, it's not obvious how to do this. It seems that if you fill a comment then go to attachments, the comment is lost
No - the "problem" is that bugzilla automatically displays the next bug in your search list. You have to click "go back to bug #..." manually. While this can be a useful feature, it can also be confusing :-( Hmm, is there an option to switch it on/off per user? Bugzilla experts?
after "need info", the reassignment should be made much more visible, I forgot it all the time :-(
There's a checkbox directly below the input field for your comment. But I can confirm that many users forget to reset needinfo :-/ What do you propose as "more visible"? Font size 500%, blinking and flashing? ;-)) Regards, Christian Boltz -- Wenn du beim Autofahren ein "komisches Geraeusch" hoerst und stehen- bleibst (ohne das Geraeusch naeher identifizieren zu koennen!), dann schraubst du ja auch nicht einfach mal auf Verdacht an der Nockenwelle rum, wenn's doch nur am leeren Tank liegen koennte! [David Haller in suse-linux]
Christian Boltz wrote:
What do you propose as "more visible"? Font size 500%, blinking and flashing? ;-))
on my screen it's really very small :-) but don't you think it should be quoted by default? as there so many non relevant answers? You know better than me :-) :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
For example, bug #168293 is noted "NEW" and "Fixed in Milestone" what does this mean? if the bug is fixed, why is it not quoted "FIXED" in place of NEW? because it's not fixed right now, and it's a wiki bug... (that prevent me from founding the "bug" pages of the wiki :-))) thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
Hello, Am Sonntag, 23. April 2006 18:03 schrieb jdd:
For example, bug #168293 is noted "NEW" and "Fixed in Milestone"
I see: Status Fixed in Milestone NEW --- This means the "fixed in milestone" field is empty ("---"). Besides that, the "fixed in milestone" is sometimes used as "must be fixed in milestone" ;-) Regards, Christian Boltz -- File Not Found.....Loading something that looks similar
Christian Boltz wrote:
Hello,
Am Sonntag, 23. April 2006 18:03 schrieb jdd:
For example, bug #168293 is noted "NEW" and "Fixed in Milestone"
I see:
Status Fixed in Milestone NEW ---
This means the "fixed in milestone" field is empty ("---").
Besides that, the "fixed in milestone" is sometimes used as "must be fixed in milestone" ;-)
Regards,
Christian Boltz oh... ok, thanks jdd
-- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
participants (2)
-
Christian Boltz
-
jdd