On Jun 28, 10:32 am, "Christopher Taylor" <[EMAIL PROTECTED]> wrote:
> John,
>
> MOST of what you are talking about is currently possible via some of
> the plugins at Trac Hacks.  Just google it, it'll show up as the first
> hit.  If you need some assistance figuring out how to combine these
> plugins to get the desired capabilities, let me know.  I can walk you
> through it.
>
> -Chris

Thanks Chris,

I'm aware of the plugins at Trac Hacks and some of them will be used,
others may need some additional capabilities, some of them need to be
refactored to take advantage of the ticket-workflow and others are
implemented in ways that I feel are not as useful as they could be
such as the MasterTicketPlugin.

The MasterTicketPlugin which has a field that specifies all it's child
tickets but I would prefer to save the parent ticket ID in the child
object and would prefer a better approach to managing the child
tickets besides a comma separated list of IDs.  A little bit of AJAX
functionality in the parent tickets to manage the child tickets would
be very useful and would take this plugin to the next level.  I'll add
that the plugin does work just fine for simple use cases for which I'm
sure it was designed for.

There are no plugins to my knowledge to provide a UI for customizing
workflow which is understandable since it's a new feature.

I also don't believe there are any plugins to control which fields are
displayed, writeable or required based on the action the user will
perform on a ticket.  The implementation of this is fairly easy (at
least hacking it in) and I have demo code already developed.  Just
need to create a plugin and create the UI for it's administration.

Having ticket subclasses would be very useful but will be much easier
to implement with SQLAlchemy.  This would allow for a different set of
custom fields and a custom workflow for each type of ticket.  That way
you could handle bugs with a different process than say a new feature
request, or a QA task, or etc.

This last feature would also be useful for creating and managing sub
tickets.

John


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to trac-dev@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to