There are several issues here

1. New messages are created with the status "unread". I
find the name somewhat unclear/unusual/somewhat
misleading (people might have read it!): I think "open"
is a bit more common initial status in bug trackers.

2. I think resolved issues should not be implicitly
resurrected (as happens now if you add a message to a
resolved issue)

3. A bit more general issue is this: does "chatting"
status provide enough benefit to justify its being
turned on by default (it's a bit unusual and thus adds
to confusion, it clutters the interface, etc)

4. Same issue with "done-cbb". It's an uncommon term
and thus adds to confusion, it clutters the interface
and my feeling is that it's rarely used.

5. Status "Rejected" is quite common.. Would it make
sense to have it by default?


To make things worse, it's not that easy to change the
default status names, b/c they are hardcoded in several
places in the code..

Logged In: YES 
user_id=6405

You are free to make changes like these locally. The only 
places that statuses are looked up is in the 
statusauditor.py detector code installed in your tracker. 
You may edit that code to change or remove behaviour (like 
the default value for new issues, or the resurrection 
behaviour).

Logged In: YES 
user_id=971153


Sure, I understand that I can make the changes (in fact I
did them and quite happy now about roundup functionality)...

It's more of: "I like roundup and think it deserves to be
used widely, but that won't happen unless it's reasonably
useable out-of-the box" kind of argument..

And by useable I mostly mean looks familiar and not-surprising.

(Also, unless admin happens to be a python programmer, he is
likely not to even try to finish installation once he
realizes that he needs to reconfigure everything AND it
requires programming in an unfamiliar language...)

Thanks for your time anyway...

Ilya