ok, I'm just throwing the ideas out to remember to work on it later on... so
here goes:

project wide:

• number of opened (new/started) DEFECT issues (choseable color ?
  ...default red)
• number of fixed DEFECT issues (ditto ...default blue)

just something else that most projects need to track.
why? because the old fashion way of looking at a project life-cycle to know what
stage of maturity the code is in used to be to track the bugs trend. There's
some sense in doing so: track the testing effort, track how fast bugs get
solved, do we need more people to fix bugs? do we need more people to find bugs?
... this may lead to ever-more complex metrics that do not belong within hudson
but can be pointed to by way of a more high-level graph)
And everything from the past cannot be all-wrong.