Milestone Triage

Big Al

1 / 1

ChanteDuboise

1 / 1

ChodTheWacko

4 / 4

Chris Keria

2 / 2

Faust

2 / 2

GabeCunningham

2 / 2

Han

1 / 1

HorstVonBrand

2 / 2

Justin Larue <jlarue@…>

1 / 1

KZK

1 / 1

Matthias

1 / 1

Motyob

2 / 2

PowerWyrm

6 / 6

SaThaRiel

1 / 1

Timo

1 / 1

anonymous

6 / 6

anthony.staines@…

1 / 1

ashes999

1 / 1

blackdog

1 / 1

bryguypgh

1 / 1

chance2now@…

1 / 1

d_m

3 / 3

darint

1 / 1

david3x3x3

1 / 1

fizzix

2 / 2

iphone4unlock12

1 / 1

kzk

1 / 1

magnate

13 / 13

mikon

3 / 3

molybdenum

1 / 1

myshkin

3 / 3

nckmccnnll

8 / 12

pampl

1 / 1

schlittk@…

1 / 1

seebs

1 / 1

silsor

1 / 1

simonebaracchi

1 / 1

solarpower55

1 / 1

stopeatreviews6

1 / 1

taina

1 / 1

takkaria

9 / 9

vext01

1 / 1

webuyanycar16

1 / 1

ycombinator

1 / 1

This milestone is the default, and is used for all new tickets of all types. When triaged by a developer, the ticket is either confirmed and assigned a new milestone, or closed as an unreproducible bug or an undesired change.

Tickets which are eventually closed as "invalid", "duplicate", "wontfix" or "worksforme" should have their milestone re-set to Triage to avoid them contaminating reports of tickets actually fixed for a real milestone.

Note: See TracRoadmap for help on using the roadmap.