On 4/23/13, Andrej Golcov <[email protected]> wrote: > Hi, > :)
[...] > > - Implement ticket-relation as separate api not connected to ticket > fields and ticket changing action. As far as I understand, UI mockup > for BEP-0006 [1] assumes that ticket relations are manages on separate > page. > Pros: the implementation will be much more clear without big Trac patches > Cons: Duplicate workflow assumes the duplicate ticket Id as part of > the ticket changing - because ticket model does not know about ticket > relations some black magic should be implemented here - listeners + manipulators are not enough ? > any ideas are > welcome. It is hard to add ticket relations to custom queries, some extra work has to be done , yes ... [...] > > Personally, I prefer the third way - no dependency on ticket model, > ticket relations have their own API and modification UI. However there > is still an open question for me: how to implement Duplicate workflow > properly. > > Any thoughts, suggestions? > I'd rather prefer the third variant , with DB designed to support relationships for any kinds of resources (... and neighborhoods , to deal with external resources like suggested by brane before [citation needed] ;) . Many plugins I can think of will benefit of a generic resource relationships API . -- Regards, Olemis.
