[Trac-tickets] Re: [The Trac Project] #1399: Add ability to define
ticket types
The Trac Project
noreply at edgewall.com
Mon Apr 4 04:10:38 EDT 2005
#1399: Add ability to define ticket types
---------------------------+------------------------------------------------
Id: 1399 | Status: reopened
Component: ticket system | Modified: Mon Apr 4 04:10:15 2005
Severity: enhancement | Milestone:
Priority: high | Version: 0.8.1
Owner: jonas | Reporter: tomek at wetafx.co.nz
---------------------------+------------------------------------------------
Changes (by cboos):
* resolution: worksforme =>
* severity: normal => enhancement
* priority: normal => high
* keywords: => category
* status: closed => reopened
Comment:
Well, I tend to agree almost entirely with the ticket reporter.
Indeed, that's what I implemented a few month ago in #919
and use in my customized Trac.
It's true that currently one can use the ''severity'' field
to distinguish a feature request from a bug report, but, as
the reporter said, it should be made more prominent, even the
first thing to select when creating a ticket.
Not to mention the fact that when planning future releases,
it also makes sense to associate a severity to an enhancement
request (e.g. this ER is a ''blocker'' for that milestone,
don't ship without that ER, or its a ''minor'' enhancement, etc.)
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1399>
The Trac Project <>
More information about the Trac-Tickets
mailing list