UI for editing workflow

[Gervase Markham]

Myk Melez wrote:
> Nit: it seems like green and red would be better suited to indicate 
> which transitions can/cannot be made (i.e. as table cell background 
> colors) than to denote open/closed states, given their "go/stop" semantics.

I agree.

> Also, the {start} -> REOPENED transition doesn't make much sense to me 
> (which leads me to wonder whether "reopened" is really a state or, like 
> "everconfirmed," an aspect of the state history better defined as 
> something like "everclosed"), but {start} -> closed states could make 
> sense for installations that want to record bugs that they ended up 
> fixing before they got around to filing reports on them.

I think it's interesting that two of the Bugzillas I surveyed recently 
which chose to hack statuses removed REOPENED. I wonder if that state 
actually has much value over just sticking the bug back in NEW.

We could enable the {Start} -> CLOSED transitions, but it would 
complicate the enter_bug UI as it would need to provide the ability to 
set them. I suggest that, in the rare case you mention, people content 
themselves with a 2-step process.

Gerv