Hi openSUSE folks,
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5. We do this mainly for three reasons:
- to get new features and better speed - to get better customization support - to get all security holes fixed
The update will happen on September 20th, aka this weekend. From a user experience, Bugzilla version 4.4.5 is not very different to 3.4.3, but there are some incompatible changes to watch out for:
* NEEDINFO is no longer a state, but a flag. This has the advantage that a bug can have multiple needinfos set. The UI still offers the needinfo checkboxes, so you should not notice this much.
* Some states got updated to sync with upstream bugzilla:
ASSIGNED has been split into CONFIRMED and IN_PROGRESS. CONFIRMED means that you acknowlede that there is a bug, IN_PROGRESS means that you work on the bug.
CLOSED has been merged into VERIFIED.
The standard bug life cycle is thus:
NEW -> CONFIRMED -> IN_PROGRESS -> RESOLVED -> VERIFIED
* Partner IDs are stored as "See Also" URLs. There are shortcuts to add them, e.g. "FATE-2222" maps to the id in fate. There's also "CVE-XXXX" to map to the mitre server for the security inclined.
With the update come per-business unit bugzilla styles and product filtering, thus navigating to "bugzilla.opensuse.org" will get you to openSUSE's bugzilla instance in a friendly green look instead of the old wiki page.
Note that this is just a different skin for the same novell.com bugzilla, you can even configure it in the bugzilla preferences section. (In case you're wondering, there's also bugzilla.suse.com, bugzilla.netiq.com, and bugzilla.novell.com.)
Cheers, Michael.
Hi Michael,
This is great news - having our own openSUSE frontend with a potential for customising/streamlining seperate from Novell/SUSE's has been something I've been asking to see for a really long time
While I realise that these 'new' bugzillas (bugzilla.suse.com, bugzilla.opensuse.org) are really just custom frontends to the same database backend, I have one question, regarding bugzilla 'shortcodes', eg bnc#
Can we now suse bsc# for bugs we want to identify as primarily a 'SUSE' bug, and boo# for openSUSE bugs?
I quite like the idea of having 'boo# numbers' for openSUSE bugs.. has a nice halloween feel to it
Regards Richard
On 19 September 2014 17:55, Michael Schroeder mls@suse.de wrote:
Hi openSUSE folks,
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5. We do this mainly for three reasons:
- to get new features and better speed
- to get better customization support
- to get all security holes fixed
The update will happen on September 20th, aka this weekend. From a user experience, Bugzilla version 4.4.5 is not very different to 3.4.3, but there are some incompatible changes to watch out for:
NEEDINFO is no longer a state, but a flag. This has the advantage that a bug can have multiple needinfos set. The UI still offers the needinfo checkboxes, so you should not notice this much.
Some states got updated to sync with upstream bugzilla:
ASSIGNED has been split into CONFIRMED and IN_PROGRESS. CONFIRMED means that you acknowlede that there is a bug, IN_PROGRESS means that you work on the bug.
CLOSED has been merged into VERIFIED.
The standard bug life cycle is thus:
NEW -> CONFIRMED -> IN_PROGRESS -> RESOLVED -> VERIFIED
Partner IDs are stored as "See Also" URLs. There are shortcuts to add them, e.g. "FATE-2222" maps to the id in fate. There's also "CVE-XXXX" to map to the mitre server for the security inclined.
With the update come per-business unit bugzilla styles and product filtering, thus navigating to "bugzilla.opensuse.org" will get you to openSUSE's bugzilla instance in a friendly green look instead of the old wiki page.
Note that this is just a different skin for the same novell.com bugzilla, you can even configure it in the bugzilla preferences section. (In case you're wondering, there's also bugzilla.suse.com, bugzilla.netiq.com, and bugzilla.novell.com.)
Cheers, Michael.
-- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Sun, Sep 21, 2014 at 09:39:45PM +0200, Richard Brown wrote:
Hi Michael,
This is great news - having our own openSUSE frontend with a potential for customising/streamlining seperate from Novell/SUSE's has been something I've been asking to see for a really long time
While I realise that these 'new' bugzillas (bugzilla.suse.com, bugzilla.opensuse.org) are really just custom frontends to the same database backend, I have one question, regarding bugzilla 'shortcodes', eg bnc#
Can we now suse bsc# for bugs we want to identify as primarily a 'SUSE' bug, and boo# for openSUSE bugs?
I quite like the idea of having 'boo# numbers' for openSUSE bugs.. has a nice halloween feel to it
I would suggest to keep bnc# for now, lots of scripts would need to be adjusted :/
Ciao, Marcus
On Sunday 2014-09-21 22:11, Marcus Meissner wrote:
On Sun, Sep 21, 2014 at 09:39:45PM +0200, Richard Brown wrote:
While I realise that these 'new' bugzillas (bugzilla.suse.com, bugzilla.opensuse.org) are really just custom frontends to the same database backend, I have one question, regarding bugzilla 'shortcodes', eg bnc#
Can we now suse bsc# for bugs we want to identify as primarily a 'SUSE' bug, and boo# for openSUSE bugs?
I quite like the idea of having 'boo# numbers' for openSUSE bugs.. has a nice halloween feel to it
I would suggest to keep bnc# for now, lots of scripts would need to be adjusted :/
I know of just one: bwiedemann's script that scans .changes files and puts notice into the corresponding Bugzilla report. ("PKG has been mentioned in BSPRJ")
On Sun, Sep 21, 2014 at 10:18:52PM +0200, Jan Engelhardt wrote:
On Sunday 2014-09-21 22:11, Marcus Meissner wrote:
On Sun, Sep 21, 2014 at 09:39:45PM +0200, Richard Brown wrote:
While I realise that these 'new' bugzillas (bugzilla.suse.com, bugzilla.opensuse.org) are really just custom frontends to the same database backend, I have one question, regarding bugzilla 'shortcodes', eg bnc#
Can we now suse bsc# for bugs we want to identify as primarily a 'SUSE' bug, and boo# for openSUSE bugs?
I quite like the idea of having 'boo# numbers' for openSUSE bugs.. has a nice halloween feel to it
I would suggest to keep bnc# for now, lots of scripts would need to be adjusted :/
I know of just one: bwiedemann's script that scans .changes files and puts notice into the corresponding Bugzilla report. ("PKG has been mentioned in BSPRJ")
well, some openSUSE maintenance tools, OBS itself.
Of course new prefixes could be added.
Ciao, Marcus
For better visibility and differentiation, I'd prefer sle# for the Enterprise bugs, and oss# for openSUSE, the difference between bsc# and boo# is to small, and easily overlooked.
My absolute most wanted feature would be a button in the the SLE mask with the function of:
"hide all customer private data from non SLE personnel, but make bug readable for all logged in readers"
and maybe a similar button for "SECURITY" bugs on both 'zillas
- Yamaban
On Sun, 21 Sep 2014 21:39, Richard Brown <RBrownCCB@...> wrote:
Hi Michael,
This is great news - having our own openSUSE front end with a potential for customising/streamlining separate from Novell/SUSE's has been something I've been asking to see for a really long time
While I realise that these 'new' bugzillas (bugzilla.suse.com, bugzilla.opensuse.org) are really just custom frontends to the same database backend, I have one question, regarding bugzilla 'shortcodes', eg bnc#
Can we now suse bsc# for bugs we want to identify as primarily a 'SUSE' bug, and boo# for openSUSE bugs?
I quite like the idea of having 'boo# numbers' for openSUSE bugs.. has a nice halloween feel to it
Regards Richard
On Fri, Sep 19, 2014 at 7:55 PM, Michael Schroeder mls@suse.de wrote:
With the update come per-business unit bugzilla styles and product filtering, thus navigating to "bugzilla.opensuse.org" will get you to openSUSE's bugzilla instance in a friendly green look instead of the old wiki page.
Note that this is just a different skin for the same novell.com bugzilla, you can even configure it in the bugzilla preferences section. (In case you're wondering, there's also bugzilla.suse.com, bugzilla.netiq.com, and bugzilla.novell.com.)
Right now all bnc links on SLES patch finder appear broken. The from latest patch (https://download.novell.com/Download?buildid=FmwH5u8_Lvs~):
https://bugzilla.novell.com/849202 => 404 Not Found.
I understand that it is not SLES list, but I suspect same problem with openSUSE bugs as well ...
On Mon, Sep 22, 2014 at 03:52:42PM +0400, Andrei Borzenkov wrote:
On Fri, Sep 19, 2014 at 7:55 PM, Michael Schroeder mls@suse.de wrote:
With the update come per-business unit bugzilla styles and product filtering, thus navigating to "bugzilla.opensuse.org" will get you to openSUSE's bugzilla instance in a friendly green look instead of the old wiki page.
Note that this is just a different skin for the same novell.com bugzilla, you can even configure it in the bugzilla preferences section. (In case you're wondering, there's also bugzilla.suse.com, bugzilla.netiq.com, and bugzilla.novell.com.)
Right now all bnc links on SLES patch finder appear broken. The from latest patch (https://download.novell.com/Download?buildid=FmwH5u8_Lvs~):
https://bugzilla.novell.com/849202 => 404 Not Found.
I understand that it is not SLES list, but I suspect same problem with openSUSE bugs as well ...
Whoa! I don't think /849202 was ever an official way to access a bug. Anyway, I'll ask our Bugzilla folks to implement it.
Thanks for the info, Michael.
On 22.09.2014 14:22, Michael Schroeder wrote:
On Mon, Sep 22, 2014 at 03:52:42PM +0400, Andrei Borzenkov wrote:
On Fri, Sep 19, 2014 at 7:55 PM, Michael Schroeder mls@suse.de wrote:
With the update come per-business unit bugzilla styles and product filtering, thus navigating to "bugzilla.opensuse.org" will get you to openSUSE's bugzilla instance in a friendly green look instead of the old wiki page.
Note that this is just a different skin for the same novell.com bugzilla, you can even configure it in the bugzilla preferences section. (In case you're wondering, there's also bugzilla.suse.com, bugzilla.netiq.com, and bugzilla.novell.com.)
Right now all bnc links on SLES patch finder appear broken. The from latest patch (https://download.novell.com/Download?buildid=FmwH5u8_Lvs~):
https://bugzilla.novell.com/849202 => 404 Not Found.
I understand that it is not SLES list, but I suspect same problem with openSUSE bugs as well ...
Whoa! I don't think /849202 was ever an official way to access a bug. Anyway, I'll ask our Bugzilla folks to implement it.
It was an addition we did in the KDE bugzilla when moving away from debian bug tracker - and it sneaked into all kind of bugzilla installations. I use it very often too.
Greetings, Stephan
On Mon, Sep 22, 2014 at 4:22 PM, Michael Schroeder mls@suse.de wrote:
I understand that it is not SLES list, but I suspect same problem with openSUSE bugs as well ...
Whoa! I don't think /849202 was ever an official way to access a bug.
Well, I just got announcement from opensuse-security with the same link ...
Anyway, I'll ask our Bugzilla folks to implement it.
Thank you!
Hi,
when I click "Report Bug" link in OBS, I get a server error:
e.g.: https://build.opensuse.org/package/show/KDE:Qt5/libqt5-qtdeclarative Report Bug points to: https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=op...
Kind regards,
Stefan
On Mon, Sep 22, 2014 at 01:24:13PM +0000, Brüns, Stefan wrote:
when I click "Report Bug" link in OBS, I get a server error:
e.g.: https://build.opensuse.org/package/show/KDE:Qt5/libqt5-qtdeclarative Report Bug points to: https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=op...
Seems like the BU filtering is done before the arguments are matched. As the novell.com bugzilla no longer has openSUSE.org in the product list, it runs into an error.
CC to Ryan Wilson, who knows about bugzilla's internals.
Ryan, is it possible to match the procuct before the BU pruning is done? (Or not do the pruning if the argument already contains a product?)
Cheers, Michael.
To be honest, the best solution would be to change that link to the following:
https://bugzilla.opensuse.org/enter_bug.cgi?classification=7340&product=...
This will guarantee that anyone who hasn't changed their BU Filter Preferences, which I assume will be a lot of people, will see the proper page.
The error occurs because the default filter setting is to go by URL, the filter is, in the eyes of Bugzilla, a self-imposed restriction.
Ryan Wilson Application Engineer II 1800 South Novell Place Provo, UT 84606 801-861-2542 RyWilson@novell.com
Attachmate | NetIQ | Novell | SUSE
Michael Schroeder mls@suse.de 9/22/2014 8:27 AM >>>
On Mon, Sep 22, 2014 at 01:24:13PM +0000, Brüns, Stefan wrote:
when I click "Report Bug" link in OBS, I get a server error:
e.g.: https://build.opensuse.org/package/show/KDE:Qt5/libqt5-qtdeclarative Report Bug points to: https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=op...
Seems like the BU filtering is done before the arguments are matched. As the novell.com bugzilla no longer has openSUSE.org in the product list, it runs into an error.
CC to Ryan Wilson, who knows about bugzilla's internals.
Ryan, is it possible to match the procuct before the BU pruning is done? (Or not do the pruning if the argument already contains a product?)
Cheers, Michael.
-- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
On Mon, Sep 22, 2014 at 08:41:01AM -0600, Ryan Wilson wrote:
To be honest, the best solution would be to change that link to the following:
https://bugzilla.opensuse.org/enter_bug.cgi?classification=7340&product=...
Yes, it now uses bugzilla.opensuse.org.
Cheers, Michael.
On Mon, Sep 22, 2014 at 05:31:16PM +0200, Michael Schroeder wrote:
On Mon, Sep 22, 2014 at 08:41:01AM -0600, Ryan Wilson wrote:
To be honest, the best solution would be to change that link to the following:
https://bugzilla.opensuse.org/enter_bug.cgi?classification=7340&product=...
Yes, it now uses bugzilla.opensuse.org.
Hmm, I still think bugzillas behaviour is incorrect. It now uses "bugzilla.opensuse.org", but the link is still be broken if I set my BU pref to "NetIQ".
It should not use the BU filtering setting if a product is given as argument, it should only look at the user's entitlements.
Cheers, Michael.
Hello,
Am Freitag, 19. September 2014 schrieb Michael Schroeder:
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5. We do this mainly for three reasons:
Thanks for the bugzilla update and all the improvements!
I still have to get familiar with the new look (after using the "old" design for years, the new design looks a bit strange here and there ;-) but let me mention some (more or less small) issued I noticed:
- in the bug list, the bugs are no longer colored by severity (for example, "major" bugs were orange and "enhancement" were green) To answer the expected question: in the preferences, I have list_color: Site Default (color_severity) Using color_priority doesn't change or "paint" anything.
- while we are at the preferences - "list_color" and "use_bug_entry" should have a more friendly label. (BTW: what does use_bug_entry do?)
- another preference issue: the "Prefered email format" defaults to HTML (even for existing users like me). I doubt this is a good idea - can you change the default to plaintext, please?
- in the bug list, the "Product" column is basically useless - it shows "openSUSE" for 99% of my bugs. That's caused by cutting off after 8 characters, which means the interesting part (like "13.1" or "Factory" is cut off. (Yes, I noticed the tooltip, but hovering over one bug after the other is not a good way to get a quick overview.)
- the "Version" column has a similar problem - for Factory, I only see things like "13.2" (that's Milestone 0) or "20140" (which can be anything from 201401* to 201409*)
- in show_bug.cgi, having all details like product, component, hardware, URL etc. on top is a bit annoying (I always have to scroll down) - is there a way to get all those fields (including the "attachments" section) back to the bottom?
- when clicking on a field label (for example "Whiteboard"), the help is opened in the same window - I have to use the "back" button to come back to the bugreport. IMHO opening the help in a new tab/window would be nice.
- when viewing a bug, there's no obvious sign/note if a bug is "novellonly". The only hint are the "Users in the roles selected below can always view this bug" checkboxes, which aren't displayed in public bug reports. The group name isn't displayed anywhere. Can we get the more verbose note back, please?
- the favicon is wrong ;-) - currently I get the bugzilla logo, but would expect the Novell or openSUSE logo (depending on the domain)
- oh, and a funny one - in the "Bugzilla Upgrade Slidedeck", the last slide says "_Unpublished_ Work of The Attachmate Group" ;-))
After shocking you with this series of problems, I also have to mention something really positive: I'm happy to see that we finally have user lookup working for everybody :-) - you probably know that I was asking for this for years.
Regards,
Christian Boltz
Hi Christian!
On Mon, Sep 22, 2014 at 09:30:01PM +0200, Christian Boltz wrote:
Am Freitag, 19. September 2014 schrieb Michael Schroeder:
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5. We do this mainly for three reasons:
Thanks for the bugzilla update and all the improvements!
I still have to get familiar with the new look (after using the "old" design for years, the new design looks a bit strange here and there ;-) but let me mention some (more or less small) issued I noticed: [...]
I forwarded the list to Ryan Wilson, who's responsible for the technical aspects of bugzilla.
Thanks, Michael.
Hello,
Am Montag, 22. September 2014 schrieb Christian Boltz:
- in the bug list, the bugs are no longer colored by severity (for example, "major" bugs were orange and "enhancement" were green) To answer the expected question: in the preferences, I have list_color: Site Default (color_severity) Using color_priority doesn't change or "paint" anything.
In the meantime, I found a workaround for this: I told my browser to honor a local file named "user.css" [1], and added the following lines to it:
.bz_buglist .bz_Minor { color: blue !important; } .bz_buglist .bz_Major { color: #FF7700 !important; } .bz_buglist .bz_Critical { color: red !important; } .bz_buglist .bz_Enhancement { color: green !important; }
Ryan, can you add this to the "official" bugzilla CSS file, please? (Without the "!important", that's only needed for user.css.)
I'm also interested in feedback to the other things I mentioned in my previous mail - if you handle them as bugreports, please CC me ;-)
Regards,
Christian Boltz
[1] search for a config option like "custom stylesheet" - the exact wording depends on the browser you use
Thank you for the workaround.
I am writing an extension to re-introduce this visual distinction to our Bugzilla implementation. I have a bug for this enhancement in the internal Bugzilla product, but feel free to create one in the OpenSuse.org product Bugzilla component with your workaround so that the line of communication is available for the open source users.
Thank you, Ryan Wilson
Ryan Wilson Application Engineer II 1800 South Novell Place Provo, UT 84606 801-861-2542 RyWilson@novell.com
Attachmate | NetIQ | Novell | SUSE
Christian Boltz opensuse@cboltz.de 9/29/2014 2:51 PM >>>
Hello,
Am Montag, 22. September 2014 schrieb Christian Boltz:
- in the bug list, the bugs are no longer colored by severity (for example, "major" bugs were orange and "enhancement" were green) To answer the expected question: in the preferences, I have list_color: Site Default (color_severity) Using color_priority doesn't change or "paint" anything.
In the meantime, I found a workaround for this: I told my browser to honor a local file named "user.css" [1], and added the following lines to it:
.bz_buglist .bz_Minor { color: blue !important; } .bz_buglist .bz_Major { color: #FF7700 !important; } .bz_buglist .bz_Critical { color: red !important; } .bz_buglist .bz_Enhancement { color: green !important; }
Ryan, can you add this to the "official" bugzilla CSS file, please? (Without the "!important", that's only needed for user.css.)
I'm also interested in feedback to the other things I mentioned in my previous mail - if you handle them as bugreports, please CC me ;-)
Regards,
Christian Boltz
[1] search for a config option like "custom stylesheet" - the exact wording depends on the browser you use
-- dU hAsT nAtUeRlIcH rEcHt. MaN mUsS sIcH bEiM lEsEn NuR dArAn GeWoEhNeN. mAcHt DaNn KeInEn UnTeRsChIeD mEhR. [Andreas Kneib in suse-linux]
Ryan Wilson wrote on 2014-09-29 15:08 (UTC-0600):
Christian Boltz composed
- in the bug list, the bugs are no longer colored by severity (for
example, "major" bugs were orange and "enhancement" were green) To answer the expected question: in the preferences, I have list_color: Site Default (color_severity) Using color_priority doesn't change or "paint" anything.
I am writing an extension to re-introduce this visual distinction to our Bugzilla implementation. I have a bug for this enhancement in the internal Bugzilla product, but feel free to create one in the OpenSuse.org product Bugzilla component with your workaround so that the line of communication is available for the open source users.
I'd like a workaround for the workaround if there won't be a preference to turn off annoying background color variations, especially the one that depends on mouse pointer position. Right now I can't tell if there could be because the preference for list color is disabled. When I want to see bugs by characteristic I click the column heading to get them sorted by that characteristic.
Another new annoyance is access to preferences hiding in a select list that doesn't look like a select list, with an itty bitty semi-visible gray diamond as only clue to its existence. Same goes for access to the saved searches. I guess both these things are probably upstream-sourced to annoy keyboard users. :-(
FWIW, I don't recall if I ever saw the thread starter, because subject lines including [ANNOUNCE] are filtered to trash prior to opensuse* being filtered to opensuse. I just stumbled onto this looking for something else. This thread's references seem to have gotten broken, if the thread actually goes back to Michael Schroeder's Friday post that seems to have been repeated on multiple lists.
Michael Schroeder wrote:
Hi openSUSE folks,
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5.
Here is a couple of slightly odd screenshots:
http://files.jessen.ch/screenshot-bugzilla-opensuse.jpeg
Initial bugzilla screen, there is about 80% of a gecko in the upper right hand corner :-)
http://files.jessen.ch/screenshot-bugzilla-login.jpeg
The login screen, but a bit jumbled. It did improve on my second attempt:
http://files.jessen.ch/screenshot-bugzilla-login2.jpeg
Just FYI.
Per Jessen wrote:
Michael Schroeder wrote:
Hi openSUSE folks,
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5.
Here is a couple of slightly odd screenshots:
http://files.jessen.ch/screenshot-bugzilla-opensuse.jpeg
Initial bugzilla screen, there is about 80% of a gecko in the upper right hand corner :-)
That was fast, fixed already.
El 19/09/14 a las #4, Michael Schroeder escribió:
Hi openSUSE folks,
we're going to update the openSUSE bugzilla from ancient version 3.4.3 to version 4.4.5. We do this mainly for three reasons:
- to get new features and better speed
- to get better customization support
- to get all security holes fixed
I see one regression.. bugzilla used to send mail in such a way that all mail from one bug report showed up as a thread in an email client. This is not the case anymore.
On 2014-10-01 17:06, Cristian Rodríguez wrote:
El 19/09/14 a las #4, Michael Schroeder escribió:
I see one regression.. bugzilla used to send mail in such a way that all mail from one bug report showed up as a thread in an email client. This is not the case anymore.
And when I try to search for the bugs in which I have something to do (new, need info, etc), the "closed confirmed" bugs are listed. They should not.
-
Andrei Borzenkov -
Brüns, Stefan -
Carlos E. R. -
Christian Boltz -
Cristian Rodríguez -
Felix Miata -
Jan Engelhardt -
Marcus Meissner -
Michael Schroeder -
Per Jessen -
Richard Brown -
Ryan Wilson -
Stephan Kulow -
Yamaban