On Tue, 10 Apr 2001, David A. Desrosiers wrote:
> Also, I'm going to be putting up two new things on the server to
> handle both bug reports, and bug responses. RoundUp was going to be the
> item of choice to handle the bug routing,
You say that Roundup *was* going to be the item of choice. Are you
going to replace it with something else?
I was just about to start using it for all viewer bug reports and
feature requests, so I would like to know if you are going to
replace it with something else.
Some kind of user-friendly frontend to Roundup for the initial
bug report would help a lot. One BIG problem with Roundup is
that you have to give it a correct category on the subject line
when sending the bug report mail or it will require manually
intervention on the server to put it in the correct category.
One thing I added to my own copy of Roundup was a possibility
to reject a bug report. It's just a matter of adding a new
status code in bugdb.py and a color (I used red #ff0000) in
roundup.py. I would like to see something similar in the
version on our web site.
Being able to reject a bug report (or feature request) is not
only to make it possible to close a bug report for different
reasons that doesn't qualify as "resolved". It can also be
useful when you have two bug reports that are related. Then
you reject one of them and add a note that it is related to
another item (including the ID).
You'll have to do something about the "Fixer" field, too.
When you enter a name in that field and save the changes
Roundup will try to send a mail to that user by adding the
first domain in the MAILDOMAINS list (roundup_config.py) to
the entered name. Maybe you can add aliases to map the
"local addresses" to the real mail addresses.
/Mike
