KDE Switches To Bugzilla

We have recently switched our entire Bug
Tracking System
to Bugzilla. Unlike the old system, Bugzilla is based on MySQL and
thus enables advanced search
and offers many other features such as email notification and voting. However, for access to the more advanced features and for bug and comment submission, users will need an account. Fortunately, the bug wizard will automatically create an account when used for the first time. All existing bugs from the old system have been migrated to the new system thanks to the efforts of Stephan Kulow.

Dot Categories: 


by Maarten Rommerts (not verified)

Come on man! Don't be so foolish! It is a good case if GNOME and KDE start working together, instead of only looking inside our own minds. Please remeber that the true power of Linux (and all open-source) is collaboration and sharing of code.

If KDE and GNOME want to develop some stuff (like libarys) together, then we can same time, improve quality, improve intergration and make a stand against fragmention. And by tis I mean an overwelmig amount of all sort of diffent protocools, technologies, standards, toolkits, ect etc. Does this make things better? No! It is better to develop a few but realy good pieces of sotware, that intergrates and works well together.

Please, next time look a bit further and think about the real reason of Linux's power.....Colaboration and working tohether.

by Klaus Mertelz (not verified)

Ok, I'm not sure any more whether this guy is joking or not. In any case, using as much code as you can from others is A Good Thing. As long as KDE is faster than Gnome, and has better integrated applications, I will use it. Think of it like that: If people not directly working for KDE (e.g. the Gnome Team) produce 75% of KDE's code, the KDE team can concentrate more on the 25% that make the actual user experience of KDE.

by Gervase Markham (not verified)

I'm one of the Bugzilla developers. Here are some neat Bugzilla features that you might want to use:

- list of the most frequently reported bugs (those with the most duplicates). Good for potential bug-filers to look at.

You can change multiple bugs at once, when logged in with sufficient privileges - see the option at the bottom of the buglist page. Great for mass-reassignments if a coder leaves.

If you change the columns on your buglist (colchange.cgi), Bugzilla remembers which ones you last chose.

If you use Mozilla (perhaps quite unlikely round here), there's a Bugzilla sidebar with a load of neat features. However, it needs a small bit of JS to fire off the installer, which has been removed from the front page. If you want it, ask for it back.

You can save regularly-run queries (see the bottom of query.cgi) and have them appear in your page footer, for one-click access to "Bugs Assigned To Me" or something like that.

You can control exactly when Bugzilla sends you email, about what events - head over to the user preferences.

You can get bugs as XML:
or buglists as RDF (add &format=rdf to your query string.)

Individual comments are hyperlinked using anchors, so you can refer to them in emails etc. Bugzilla also autolinkifies comments in several neat ways, so text such as "bug 123, comment 4" or "http://www.google.com" will become a link without you needing to type any nonsense.

Hope those are useful :-)


by Daniel Naber (not verified)

> http://bugs.kde.org/duplicates.cgi

Thanks, I think we have an even better solution for that which avoids duplicates before they are submitted: our wizard uses the summary's words to search for similar bugs. It uses MySQL full-text search for that, i.e. bugs with most similar summaries will be most relevant and thus be listed on top.
You just have to add a full-text index for that. The code for the wizard is here: http://webcvs.kde.org/cgi-bin/cvsweb.cgi/bugs/bugz/

by Aaron J. Seigo (not verified)

the RDF feature is sweet! now i can watch my bugs scroll across my panel in the newsticker. heh...

by Bijumon V Gopalan (not verified)

How to handle test cases in bugzilla ?

by MrFoo (not verified)

Great move. That old bug tracking system was _really_ bad.

by . (not verified)

... but the old one was simple to use to report bugs. the new one requires login.

by MrFoo (not verified)

No more closed bugs with just a (Done), links between duplicates, easier queries to find out if a bug as already been reported, the possibility to follow bug reports by adding yourself to the Cc. I think a simple login requirement is nothing compared to the benefits.

by Hakenuk (not verified)

- no offline posting of bugreports

- not easy for beginners

- overloaded for small project modules

- no annonymous posting

- gui is crap

by Stof (not verified)

> - not easy for beginners


And bug reporting is not supposed to be for beginners. A small amount of GOOD bug reports is better than large amounts of bad reports.

> - overloaded for small project modules

Makes it easier to seperate things.

> - no annonymous posting

Prevents people from posting crap.

> - gui is crap

Unless you're the developer.

by Peter (not verified)

> > - no annonymous posting
> Prevents people from posting crap.

Not only that, but also gives the developer a hand to get information not in the bug report itself.

And having a mail alias for bugreports doesn't sound bad in my ears.

by Amanuel Zaid (not verified)

hay,its me who wants a lesson and theory of off-line editing and on-line editing.could you help me please? becouse i need to be more educated in this field.can you help me?