#869: Cumulative patch: New workflow system for tickets in Trac
---------------------------+------------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jonas
Type: defect | Status: new
Priority: high | Milestone:
Component: ticket system | Version: devel
Severity: normal | Resolution:
Keywords: workflow |
---------------------------+------------------------------------------------
Changes (by [EMAIL PROTECTED]):
* severity: critical => normal
Comment:
Hello,
My name is Christian Sprajc and I'm Project Manager of the Open Source
Project "PowerFolder" (http://www.powerfolder.com). We use Trac since
three weeks and we like it very much. Thanks for this nice and useful
Product.
I'm looking forward to the Workflow component. I have read the
"Whitepaper" of "New Trac Workflow" and I think something is still
missing. I have the some Ideas to improve the "New" part of the workflow,
the way a ticket comes into the system.
We have the problem, that someone who enters the ticket (a user or
developer) is not responsible for sheduling a ticket on a milestone or
version. Futhermore he might not have an idea to what component this
ticket belongs to, nor what priority/Severity a ticket has. He also should
not assign the ticket to a user.
I am thinging about a "Simple ticket entry" where all these properties
have defaults which cannot be changed by the user. This ticket should then
be evaluated by the project management, which sets these properties.
Workflow would be then:
"Simple Ticket entry" (User, Developer) -> "Evaluation and assignment"
(Project management) -> "Ticket new"
Best regards,
Christian Sprajc
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/869>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
