- issue2550926 - Original author adding a second message shouldn't set status to 'chatting'. Updates to jinja and classic tracker's statusauditor.py and new config.ini for the detectors. Also updated upgrading.txt. Tested classic tracker using demo.py. Test cases: value set to false: second update sets to chatting value set to true: update by new user sets to chatting, update by creator of issues leaves it at unread. missing config value in config.ini: error about missing value value set to non-boolean: error message reports bad value with valid values.

def init_severity(db, cl, nodeid, newvalues):
    """Make sure severity is set on new issues"""
    if 'severity' in newvalues and newvalues['severity']:
        return

    normal = db.severity.lookup('normal')
    newvalues['severity'] = normal

def init(db):
    db.issue.audit('create', init_severity)