view website/issues/detectors/severityauditor.py @ 5133:85eee1f236b2

I had an incorrect fix for issue2550601. Changed schema to define class patches not patch. Changed commented out patches section in bug.item.html to use patches-1 an not patch-1 as a result of schema changes. The show open Milestones link had a leak of the @group value. If you clicked on show open tasks or show open bugs they group by priority. The url being formed for show open milestones was inheriting the @group if you were on an index page for bugs or milestones. Explicit set the @group to status (which a milestone does have) prevents the @group=priority from being applied to a milestone index page which results in a red error banner stating priority is an invalid param for milestones. ./demo.py -t devel now runs without obvious breakage.
author John Rouillard <rouilj@ieee.org>
date Mon, 04 Jul 2016 18:19:51 -0400
parents c2d0d3e9099d
children 0942fe89e82e
line wrap: on
line source


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

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

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

Roundup Issue Tracker: http://roundup-tracker.org/