Christian Boos kirjoitti:
> Lucas Eisenzimmer wrote:
>> I was just wondering whether you have a rough date in mind when Trac 0.12
>> might be stable. We are using Trac for requirements engineering and we would
>> need 'real' ticket type depending workflows. Theoretically, the triage
>> function of the AdvancedTicketWorkflowPlugin would do it, but for several
>> ticket types with own, separated workflows it starts to get confusing and
>> buggy very fast.
>>
>
> Granted, I also think that separated workflows for each ticket type are
> clearer when you need them, which leaves open the problem of how to
> transition from one such workflow to another when the type changes.
For example Redmine (that get's referred lot nowadays) has very
"complex" workflow engine. You can have per issue type, per role
configurations. But Redmine _doesn't_ allow change of issue type. But
instead there is copy option where you have possibility to change type.
This leads to very philosophical question:
Is ticket, once issued, on the system locked to type it has? Currently
Trac is very liberate in this sense and allows change of issue type
which fits well to "staying away" philosophy.
Restrictions like different workflows pushes Trac usage to more "getting
in a way" philosophy.
I see following solutions to this:
* Don't allow type change
* Require default state for each ticket type and set that in
case of change
* Add change-on-copy functionality (similiar to Redmine)
* Complex rules translating between states.
Translation is not even trivial. If you think of following:
If we have enhancement states like:
'new', 'accepted', 'rejected' and 'implemented'
And bug states like:
'new', 'accepted', 'invalid', 'testing', 'fixed'
There is not much common... So it would lead to one more factor: You
need to be able to restrict type to change depending on current state.
This would be ultimate solution but might require more than just a plugin...
>> In http://trac.edgewall.org/ticket/6548 I read that this functionality has
>> been assigned to milestone 0.12. Is this up to date and do you think you
>> could make a rough point about a release date for Trac 0.12?
>>
>
> No, it's not up to date. Like for many other tickets, a rescheduling
> will be done in the coming days.
>
> Besides, take http://trac.edgewall.org/ticket/6548#comment:3 to be an
> idea for implementing an alternative to the ConfigurableTicketWorkflow
> component (i.e. the main default ITicketActionController), which can be
> done as a plugin.
> So I've cleared the milestone for this ticket ("no milestone" means for
> us "unseen so far", "2.0" means "eventually later").
But if this can be done in a plugin, it should be done as one and later
on migrate to Trac.
--
Jani Tiainen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
