Hi,

#844 is not related to master tickets, but #886 is so I'll assume that's
what you were referring to.

Though it may seem unrelated, the workflow sandbox now (since [2850])
provides an ITicketManipulator extension point. This allows manipulation
of tickets and ticket fields prior to display, as well as validation. The
manipulators are stackable, so as long as they don't touch conflicting
fields it is entirely possibly to have a a manipulator that handles
ticket dependencies, and another that handles a more useful "duplicate"
field, etc.

I've whipped up a quick plugin leveraging this architecture, which
handles parent/child dependencies. You can try if you like, just check
out the workflow sandbox:

    svn co http://svn.edgewall.com/repos/trac/sandbox/workflow

Install as usual with Trac. Then download this:

    http://swapoff.org/files/tracticketmojo-0.1.tar.gz

And install as you do any Trac plugin.

It will require a Trac environment upgrade to add the custom "parent"
and "children" fields. This could easily be stored in a database table,
but I couldn't be bothered at the moment.

It currently has the following behaviour:

  - Parent tickets can not be closed until all children are closed.
  - Reopening a child ticket reopens all parent tickets.
  - Closing the last open child ticket will close a parent ticket.

It works for me, but YMMV.

Alec

On Mon, Jan 30, 2006 at 09:33:06PM +1100, [EMAIL PROTECTED] wrote:
>   Is anyone planning to implement Master Tickets? What roadblocks are there 
> for doing this work?
> 
> Is it a resource issue, a low priority or too hard?
> 
> I would like to help get this going.
> 
> Cheers
> 
> Alec
>               
> ---------------------------------
> Do you Yahoo!?
>   Find a local business fast with Yahoo! Local Search
> _______________________________________________
> Trac-dev mailing list
> [email protected]
> http://lists.edgewall.com/mailman/listinfo/trac-dev


-- 
Evolution: Taking care of those too stupid to take care of themselves.
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev

Reply via email to