Hi,
I tried that approach also, but since I don't want to break any agilo
feature, I looked for other work around.
If the model is the one that changes and that's the reason Agilo is
not working with the importer plugin, we just need to adapt the plugin
to use the Agilo ticket model. There is the changes that I made to the
TicketImport plugin and it works for me, I also tried this kind of
solution for the BatchModifyPlugin and also works.
Changes :
------------------------------------------------
diff importer.pyBACK importer.py
19c19
< from trac.ticket import TicketSystem
---
> from agilo.ticket.api import AgiloTicketSystem
20a21
> from agilo.ticket.model import AgiloMilestone
83c84
< 'fields': ['ticket or id'] +
[field['name'] for field in
TicketSystem(self.env).get_ticket_fields()] }
---
> 'fields': ['ticket or id'] +
[field['name'] for field in
AgiloTicketSystem(self.env).get_ticket_fields()] }
176c177
< tracfields = [field['name'] for field in
TicketSystem(self.env).get_ticket_fields()]
---
> tracfields = [field['name'] for field in
AgiloTicketSystem(self.env).get_ticket_fields()]
178c179
< customfields = [field['name'] for field in
TicketSystem(self.env).get_custom_fields()]
---
> customfields = [field['name'] for field in
AgiloTicketSystem(self.env).get_custom_fields()]
266c267
< ('milestone', model.Milestone),
---
> ('milestone', AgiloMilestone),
------------------------------------------------
diff processors.pyBACK processors.py
9c9,10
< from trac.ticket import Ticket, model
---
> from trac.ticket import model
> from agilo.ticket.model import AgiloMilestone
130c131
< class CurrentLookupEnum(model.Milestone):
---
> class CurrentLookupEnum(AgiloMilestone):
------------------------------------------------
diff ticket.pyBACK ticket.py
7c7,8
< from trac.ticket import Ticket, model
---
> from trac.ticket import model
> from agilo.ticket.model import AgiloTicket
9c10
< class PatchedTicket(Ticket):
---
> class PatchedTicket(AgiloTicket):
------------------------------------------------
Sorry for don't attach it as a patch but the idea is to be able to
change any plugin to works with the Agilo Ticket model.
Regards,
Jose Luis.
On 6 jul, 18:51, Stephan Richter <[email protected]> wrote:
> On Monday, July 05, 2010, Adolfo González Blázquez wrote:
> > Is it possible that you send that patch so we can use it?
>
> Sure. Attached you find the patch. I do not guarantee that it fixes all
> plugins
> and does not break the burndown update behavior. Well, I know for sure it
> disables the burndown update for ticket import, but that's okay for me. I also
> removed trailing whitespace in one file, so that's the reason for the many
> whitespace changes.
>
> Regards,
> Stephan
> --
> Entrepreneur and Software Geek
> Google me. "Zope Stephan Richter"
>
> agilo-1.3.0.3-fix-ticket-import.patch
> 3 KVerDescargar
--
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-scrum
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Scrum" Google Group. This group is focused on
supporting Agilo for Scrum users and is moderated by
agile42 GmbH <http://www.agile42.com>.
To post to this group, send email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo
