On Jun 29, 1:35 am, Felix Schwarz <[email protected]> wrote: > Am 26.06.2009 01:26, schrieb yoheeb: > > > we are not a fully scrum based group. We like to use some agile > > features (burndown, backlog) etc. but we dont' use sprints, and some > > other things. One of the things we really like are Agilo's linked and > > calculated ticket fields. (traceability is nice, would love a true > > traceability report) Is it possible to pull in these parts of agilo > > to a standard trac, or is it all or nothing? > > We decided to go with the integrated approach to keep complexity simple > so for now it's indeed 'all or nothing'. However the parts are mostly > separated from the rest of Agilo in agilo.ticket so you can try to > extract them from Agilo and use them separately.
Bummer > > Of course it would be even better to have an API within trac so that we > can extend trac more cleanly (then you probably could take our > implementations very easily and use them in a separate plugin). However > this would requires: > - convince trac developers that ticket *types* are more than just > setting one field > - different fields per ticket type > - non-writable fields (calculated ones) > well, it can be done in the current trac api. The TimingAndEstimation plugin does it of it's "Total Hours" field. There is a Change listener, and a ticket template, I think that's all thats done for that one. Of course, in the Case of Agilo, I suspect you may need a couple more listeners/renderers. And I know it also is more complex given that it is all configurable via the .ini file. Ahh well. > > Sorry I can't just try > > > it, last time I tried agilo, it affected all my installs since we use > > mod_python and not the mod_wsgi method agilo needs (or needed at hte > > time anyway) to support a multi-repo setup that doesn't apply agilo > > mods to all of them. > > We fixed a couple of issues related to 'environment pollution' so you > might want to try again. > Good to know. Given the fact that it's Currently "All or nothing", in my case, doesn't do me any good. There are just a couple too many "scrum specific" features for me to be able to pull out given the resources I have available. I'll still probably install it to see all the progress. this project has been evolving nicely. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
