[OpenLayers-Dev] ticket state
bluecarto at gmail.com
Thu Dec 13 05:02:13 EST 2007
What I would suggest is to add a new option into the ticket properties.
In the options available in the trac config it would be possible to
add ticket-custom fields. Some should be already available but
commented out :
#stage = select
#stage.label = Triage Stage
#stage.options = Unreviewed|Needs more info|Needs design
decision|Accepted|Ready for review
#stage.order = 5
#stage.value = 0
I find those options significant and the "triage stage" name looks good to me.
I also proposed to use it for the MapFish project.
What do you think about that ?
On Dec 12, 2007 8:48 PM, Eric Lemoine <eric.c2c at gmail.com> wrote:
> On Dec 12, 2007 8:39 PM, Tim Schaub <tschaub at openplans.org> wrote:
> > Hey-
> > We currently use the keywords field to represent ticket state. Things
> > like "commit", "review", and "needstests" (or is it "needtests" or why
> > not simplify and just make it "test") are significant to us. Other
> > users of trac have other things in mind when they see the keywords
> > field. They write things like "fix this darnit" or other words that
> > describe the ticket for them.
> > Proposal:
> > We use the "Severity" field of a ticket (currently not used) to
> > represent the ticket state. This is a dumb word for ticket state, but
> > the field has a fixed vocabulary. Then we add words like "commit",
> > "review", and "test" - and those become options in a drop-down. Of
> > course users will probably still set those willy-nilly, but at least we
> > wouldn't get arbitrary words in there. Guess it would make sense to
> > have a default "in queue" state or something.
> > No biggie if others like the keyword slop. I can put up with it.
> +1, but I can definitely live with the current way.
> I think having a default "in queue" is important, otherwise I fear
> that people filling tickets will just pick one out.
> Dev mailing list
> Dev at openlayers.org
More information about the Dev