On Fri, Jan 12, 2007 at 12:36:15AM +1100, Dave Cole wrote:
> I cannot see a clean way to configure the ticket actions via a plugin.
> Should the TicketSystem.get_ticket_actions() be implemented via an
> ExtensionPoint delegate?
>
> More generally, should the ticket permissions/actions and status be
> implemented in something like an ITicketWorkflowProvider with the
> current functionality enclosed in something like
> DefaultTicketWorkflowProvider? That would remove all of our hacks to
> ticket/api.py and ticket/web_ui.py (except for the ability to edit owner
> at will).
The old WorkFlow code introduced a whole slew of extension points for
ticket workflow including ITicketActionController, which addresses this
specific issue. This is what I assumed you were referring to in your
earlier mail, and thus my confusion.
The diff against (old) trunk r3378 is here:
http://trac.edgewall.org/changeset?new=3378&new_path=sandbox%2Fworkflow&old_path=trunk#file41
--
Evolution: Taking care of those too stupid to take care of themselves.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
