Hi Andrea! Do you have any estimative on when will the integration begin to show up? I really need it to implement Agilo at my company, as we already use Mylyn for tracking Trac tickets :/
I've tried to use it already, something works properly, but others (like Sprint listing, that doesn't even appear as a field on the New Task dialog and appears blank when editing a ticket) don't, and that don'ts keeps me from implementing it for all our teams. Thanks in advance On Jul 23, 5:45 pm, Andrea Tomasini <[email protected]> wrote: > On 23 Jul, 2009, at 17:25 , Chris wrote: > > Hi Chris :-) > > > Any chance Agilo could integrate with the Trac MasterTicketsPlugin? > > >http://trac-hacks.org/wiki/MasterTicketsPlugin > > > The Master Tickets Plugin establishes a simple hierarchy of > > dependencies between tickets. It provides an interface to GraphViz > > for a graphical view of the dependencies. > > As you mentioned later this overlaps with the links plugin, of course > we do not provide a GraphViz... > > > More importantly for me, the EclipseMylynproject integrates with the > > MasterTicketsPlugin to show task dependencies for Trac tasks within > > Eclipse. > > That we will improve soon, there will be soon a special AgiloMylyn > Integration ;-) > > > I believe all that would be required is to allow customizability of > > your internal custom field names for "o_links" (References) and > > "i_links" (Referenced By). > > It is not only that, there are a lot of "rules" inferred from the link > module, it basically regulate the whole backlog hierarchy, ticket type > based dependencies, it is a core part of the datamodel to implement > full traceability... > > > > > The MasterTicketsPlugin uses the fields "blockedby" and "blocked" to > > do essentially the same thing (possibly slightly different semantics, > > but I would use them the same way in my project). > > > The labels can display the same in Agilo, only the internal database > > field name would need to change. > > > Possible defaults in trac.ini: > > [agilo-links] > > field.incoming_links = i_links > > field.outgoing_links = o_links > > > [ticket-custom] > > i_links = text > > i_links.label = Referenced By > > o_links = text > > o_links.label = References > > > which could be overridden for MasterTickets (and Eclipse/Mylyn) > > integration with > > [agilo-links] > > field.incoming_links = blocking > > field.outgoing_links = blockedby > > > [ticket-custom] > > blockedby = text > > blockedby.label = References > > blocking = text > > blocking.label = Referenced By > > > Does that make sense, and would it be easy to do? > > May be you can just try to add the MasterTicketPlugins on top of > Agilo, and disable the link module... I guess something really wired > will happen but could be a starting point. In any case if what you > miss is theMylynintegration, we have a plan for that, whoever is > willing to contribute is very welcome ;-) > > > I have also submitted a request for the MasterTicketsPlugin to be > > customizable in the field names that it uses. > > I see, but as said above it is not only a matter of field the > approaches are pretty different ;-) > > > However, I think that the Eclipse/Mylynproject would also have to > > make changes to accommodate the alternate field names, so I believe it > > would be easier for Agilo to provide the integration customizability > > directly, as described above. > > And that is what we will do, it is just about making an extension to > the XMLRpc plugin of Trac, and put in there the Ticket typing... and > the visible and invisible fields :-) > > Looking forward to the number of people willing to have an AgiloMylyn > integration ;-) > > > Thanks, > > YAW > > > Chris > > ANdreaT --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. 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/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
