Here's another user that would be very happy to see Mylyn
integration. ;)

On Aug 24, 9:56 pm, Dr Joe Karthauser <[email protected]> wrote:
> I am very interested in this too. I guess that there are some user  
> stories about it!
>
> Joe
> --
> Dr Joe Karthauser
>
> On 24 Aug 2009, at 17:42, Chris <[email protected]> wrote:
>
>
>
> > Any update on the priority / road map status of an Agilo / Mylyn
> > integration?
>
> > Looking on the development wiki / Backlog, the only reference I can
> > find to Mylyn is in an old ticket #286:
>
> >https://dev.agile42.com/ticket/286
>
> > Are there plans to work on this any time soon?
>
> > Thanks,
>
> > Chris
>
> > On Jul 28, 9:07 am, Chris <[email protected]> wrote:
> >> Thanks Andrea!
>
> >> On Jul 23, 4:45 pm, Andrea Tomasini <[email protected]>
> >> wrote:
>
> >>> On 23 Jul, 2009, at 17:25 , Chris wrote:
> >>>> Any chance Agilo could integrate with the Trac 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...
>
> >> For your prioritization, the links / GraphViz isn't that critical to
> >> me (more of a nice to have).  TheMylynintegration (below) would be
> >> great!
>
> >>>> 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 ;-)
>
> >> That's great!  That's really what I'm looking for.
>
> >> Any idea on timeframe / progress so far?  (I know that since your  
> >> team
> >> itself works with Agile sprints, it can be hard to pin down an exact
> >> target date, but is this something being worked on in the current
> >> sprint, or is it on the roadmap for future work?)
>
> >> Will it be part of the open source Agilo project, or only in Agilo
> >> PRO?
>
> >> ...
>
> >>> 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 ;-)
>
> >> ...
>
> >>>> 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 ;-)
>
> >> Great!
>
> >> Does the Trac XMLRPC plugin currently give you the ability to get the
> >> custom "select" list for things like Sprint name?
>
> >> Besides not seeing the nesting of "blocking" tickets (as described
> >> above), the other major problem I have run into withMylynand Agilo
> >> is that the Sprint name list does not get populated, so it never  
> >> shows
> >> up when looking at the ticket in Eclipse (and makes it impossible to
> >> properly create a new ticket and assign it to a sprint).
>
> >> Chris

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to