Bugzilla training scripts

Matěj Cepl, mcepl@redhat.com

Red Hat

What’s wrong with bugzilla?

  1. NOT MUCH (comparing to others)
  2. As every webapp, completely inflexible
  3. Online-always required
... comparing to others
mention JBoss switch from JIRA
and Trac for large projects is no go.
There are many completely and quite conflicting requirements on it.
Webapps as the main tool for actuall full-time job

Proposed other solutions

Used inside of Red Hat by developers
Task management tightly coupled with Eclipse IDE.
Much simpler version of what I do is server-side on b.g.o
Great for organizing bugs in tasklist-style way (plus team view, synchronization with corporate development schedule etc.).
In the end leads back to the standard bugzilla bug page.
Works offline, again in the organization of bugs, much improved task management.
However, again, when you get to the individual bug itself, form is probably even worse than in Firefox. And improvements are possible only with real Java programming.
Subset of what I do in my scripts (actually looking )
WAIDH screen shot
Mylyn screen shot

Comments on bugzilla.gnome.org

  1. Is it component configurable or configurable for individual users?
  2. Much more than buttons
  3. The only downside: depends on Firefox; but is it a downside?

Design principles

  1. It should be working in different bugzillas and for different workflows
  2. Therefore, all business logic should be outside of the script
  3. Rolling upgrades, constant refactoring


bugzilla.redhat.com / Ordinary bug triager
Just very simple:
  1. background colors (rawhide, fedora, RHEL, RHEL/IT, security)
  2. Comment boxes
Just to show that it works and scroll down comments
bugzilla.redhat.com / me
Complete presentation:
  1. Mark triaged
  2. set needinfo
  3. automatic assignee
  4. emphasize bad components (#616938)
  5. me in CC list (#616161)
  6. Close upstream
  7. Push upstream
  8. Query local / upstream
  9. bad MIME attachments (#485145)
  10. configuration
  11. fill in chips
  12. Xorg.log analysis
  13. timesheet generation