Able to file bug as Expired

[Jonathan Lange]

When I go to file a bug in Launchpad, I'm presented with a bunch of Extra options that I can set. One of these options is Status.

It allows me to file a bug as New, Incomplete, Invalid, Won't Fix, Expired, Confirmed, Triaged, In Progress, Fix Committed or Fix Released.

Filing a bug as Expired makes no sense :)

This is on edge. Not sure about lpnet.

[Bryce Harrington (bryce)]

Fwiw, this appears when I file a bug against launchpad, but not when I try filing it against a source package in ubuntu.

[Bryce Harrington (bryce)]

Ah, according to bugtarget-filebug-views.txt only bug supervisors see the status option; perhaps I'm just not in the appropriate group to see this for ubuntu.

[Bryce Harrington (bryce)]

Yeah, after a bit more experimentation locally, it seems to only be shown when logged in as the bug supervisor for the project.

[Bryce Harrington (bryce)]

Hmm, EXPIRED is definitely listed as a status permitted to bug supervisors, in addition to WONTFIX and TRIAGED. (bugtask.py line 329, BUG_SUPERVISOR_BUGTASK_STATUSES)

So... while it may seem weird to be able to file the bug as status expired, it seems to be entirely permitted, just as you could file a bug as wontfix or invalid. The capability is limited to only bug supervisors, who presumably are going to know what the heck they're doing. Maybe it should be left as is? What do you think?

[Robert Collins (lifeless)]

This is basically shallow polish; needs a vocab *just for the web* - API calls should be allowed to create a bug in anystatus (consider e.g. mirroring processes).