On Sep 3, 2:24 am, Andrea Tomasini <[EMAIL PROTECTED]> wrote: > On 2 Sep, 2008, at 23:34 , [EMAIL PROTECTED] wrote: > > > Hi, > >>http://trac-hacks.org/wiki/AgileTracPluginseems to be an interesting > >> approach to tackle agility, see alsohttp://www.agile-trac.org/roadmap > >> . > > > from a complete user perspective I see some overlap with another agile > > modification (seewww.agile42.com). While choice is good, I think a > > lot > > of projects replicate similar work that belongs to the trac core in my > > opinion. > > I am partly committed to agile42, therefore I will limit my comment in > agreeing that the majority of the changes we made in agilo to make > Trac a bit more flexible and articulated, could be easily ported to > the core, and honestly I would expect so. Fundamental aspects such as: > > - Ticket typing > - Ticket linking > - Separation of Edit/View to ease the handling of tickets, including > collapsiblehistory... none likes to scroll three pages to see the > lastchange... do you? > > We also developed in the last version a concept for Backlog, a very > useful tool in Lean/Agile that has to allow to sort ticket arbitrarily > as well as following some specific criteria... and neither the Report, > nor the Ticket Custom Query allow to assign arbitrary priority, > neither to edit multiple tickets at once... typical the Sprint Backlog > at the Daily Stand-Up Meeting. > > We will be very glad to cooperate with EdgeWall guys, but so far we > didn't made it through, may be we will need to have a bit more of > sponsorship :-) > > Best > ANdreaT > > P.S: A tab with version is coming very soon ;-)
I have tried your tool, and I like it. I don't expect it to ever be part of the core,however. I also did have some issues. Simply put, the fact that the plugin, although installed as a stand alone plugin (and not a global one) screwed up all the other projects in a multi- project environment was concerning. Also the fact that you modified something so that closed tickets no longer had a line through them, just a grayed background in reports was of issue. but, these are minor things, considering it is still pre-release beta, and I am confident your team will iron them all out. The biggest thing regarding this post you made, is that you would "expect" items x,y,z to make it into the core is potentially an issue with working with the trac team. while I think your enhancements are really good, the simple fact that they aren't for everyone and therefore don't belong in the core. In particular: "ticket typing" is there, just not in your context, "ticket linking" is not a feature that should be in the core, since not everyone has need for it, and it CAN be achieved by a fully stand-alone plugin (MasterTickets), and separation of the edit/view, to me, was a pain. Now, I could see it as a useful OPTION, particularly if you could separate that by view vs edit permissions, but again, not really a CORE type feature. The trac team seems to of worked extremely hard to make the "core" very vanilla, and with good success, I would more expect you to get a lot more input on how to make it a true plugin, which doesn't break things, which would still be welcome. I really like the flexibility you're tool does offer, it's just not quite there yet. Hence the beta status, but I do hope to see more, it's a very well thought out, like I said "flexible" tool. I don't see how custom workflows fit in however. Keep up the good work! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
