See http://trac-hacks.org/ticket/8550 for a fix to this particular error.
I'm trying to use it with Mylyn ; alas, after fixing this I cannot submit
tickets due to further issues, but at least I can view them now.
The next issue is that the Trac Mylyn connector (or maybe Mylyn itself) does
not distinguish between the Agilo ticket types. This means that it presents
all the custom fields for consideration for all tickets, although each
ticket type has it's own fields, and returns them when you submit the
ticket. The backend runs into an error when you do this ; because you are
returning fields which are not in the custom field list (for that ticket
type) it tries to put them in the main ticket table, and fails because there
is no field of that name.
e.g. "no such column drp_resources"
A first step might be ignoring these columns, but they would still be
present in the UI at the client ; what really needs to happen is that Mylyn
needs to know about different ticket types.
It also occurs to me that Mylyn knows about the master ticket plugin and
it's sense of ticket relationships but I'm not sure what it will think of
the Agilo ones.
Using the web connector rather than the XMLRPC connector does work ; it's
not ideal though.
------
2011-10-23 12:47:11,827 Trac[xml_rpc] ERROR: Traceback (most recent call
last):
File
"/usr/lib/python2.5/site-packages/TracXMLRPC-1.1.2_r10706-py2.5.egg/tracrpc/web_ui.py",
line 158, in _rpc_process
result = (XMLRPCSystem(self.env).get_method(method_name)(req, args))[0]
File
"/usr/lib/python2.5/site-packages/TracXMLRPC-1.1.2_r10706-py2.5.egg/tracrpc/api.py",
line 197, in __call__
result = self.callable(req, *args)
File
"/usr/lib/python2.5/site-packages/TracXMLRPC-1.1.2_r10706-py2.5.egg/tracrpc/ticket.py",
line 245, in update
t.save_changes(author, comment, when=when)
File
"/usr/lib/python2.5/site-packages/agilo-0.9.5-py2.5.egg/agilo/ticket/model.py",
line 763, in save_changes
res = super(AgiloTicket, self).save_changes(author, comment, when, db,
cnum)
File "build/bdist.linux-i686/egg/trac/ticket/model.py", line 289, in
save_changes
@self.env.with_transaction(db)
File "build/bdist.linux-i686/egg/trac/db/api.py", line 77, in
transaction_wrapper
fn(ldb)
File "build/bdist.linux-i686/egg/trac/ticket/model.py", line 336, in
do_save
% name, (self[name], self.id))
File "build/bdist.linux-i686/egg/trac/db/util.py", line 65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
File "build/bdist.linux-i686/egg/trac/db/sqlite_backend.py", line 78, in
execute
result = PyFormatCursor.execute(self, *args)
File "build/bdist.linux-i686/egg/trac/db/sqlite_backend.py", line 56, in
execute
args or [])
File "build/bdist.linux-i686/egg/trac/db/sqlite_backend.py", line 48, in
_rollback_on_error
return function(self, *args, **kwargs)
ServiceException: no such column: drp_resources
--
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
Agilo Software GmbH <http://www.agiloforscrum.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