On 5 Aug, 2009, at 21:21 , Ash wrote:
HI Ash,
> I'm testing out the Agilo plugin, and running into a number of issues
> with it.
>
> All issues were with the Agilo PRO 1.0 RC2 binary release.
>
> 1. It's not clear on the Agilo site when you download, that you get
> different versions if you go for the pre-egg vs. the source. I can't
> actually find much documentation on what the Pro RC has extra.
> (Specifically, does it have any more free features than the 0.8
> release? Or is it only useful for people who plan to license it? (We
> haven't decided at my company if we plan to or not, so we want to
> start by gettign used tot he free functionality, before we activate
> the trial.))
Thanks for the feedback we will improve the message, do you have some
specific suggestions? I have posted a blog and also a message in the
group trying to make clear what is the goal of the Pro, and what are
the differences with the Open Source version. The Pro is a
"subscription" that as professional users of Agilo, guarantees
professional support, and SLA on response time, as well as help in how
to use, set it up, and also on how to solve process problems with
Agilo. Pro subscribers also get hotfixes to their specific bugs, as
well as security of fixes updates, also within the 2 months release
cycle. On top of this we decided to offer to the Pro users some
"premium" features, such as the digital whiteboard, the inline editing
and others which will come. Probably one day these feature will flow
into the Open Source version, but we do not know yet... :-)
> 2. If you try and do a trac-admin <dir> upgrade when you've removed
> all the ticket types, the upgrade fails. (I tried to post this earlier
> with a trace and everything, but Google ate my homework apparently.)
> Essentially, there is somewhere in Agilo's upgrade code where it
> iterates on the ticket types, and if there is none, then it bombs mid-
> upgrade. You have to manually drop the tables and try again, as you
> can't re-run the upgrade as it does makes the tables. (It also
> disables the old ticket module
I will check on this, anyway cycling on ticket types shouldn't be a
problem... the fact that disables the old ticket module is because it
has to enable the Agilo ticket module. The best way to "force" an
upgrade is to just remove the agilo row from the system table, that
should be enough to make Agilo think that it needs to install again :-)
> 3. There are no auto-created permission groups. It would be a real
> help if I there were 'Team', 'Product Owner', etc roles automatically
> created, as the number of new AGILO_* permissions is a little
> overwhelming.
Well there are, so if you do not see them, is because something went
wrong. There are predefined meta permissions called SCRUM_MASTER,
PRODUCT_OWNER and TEAM_MEMBER which encapsulate a significant set of
permissions just to get started. One can than tune and tweak those, by
adding groups containing these permissions as basis.
> 4. There is no version number listed in the About page for the Agilo
> plugin. I checked the log and looked for any missing dependencies, but
> could find none.
The version number has been fixed, and it appears at the bottom of
every page of Agilo.
> 5. There seems to be a bug in one of the underlying functions that
> reads arguments from the post requests and is creating lists of
> strings instead of strings for some calls, resulting in errors like
> 'ERROR: unhashable type: list' when I try and add a user to a team.
> Here's the traceback for it:
>
> Most recent call last:
> File "/usr/lib/python2.6/dist-packages/trac/web/main.py", line 423, in
> _dispatch_request
> dispatcher.dispatch(req)
> File "/usr/lib/python2.6/dist-packages/trac/web/main.py", line 197, in
> dispatch
> resp = chosen_handler.process_request(req)
> File "/usr/lib/python2.6/dist-packages/trac/admin/web_ui.py", line
> 113, in process_request
> path_info)
> File "/usr/local/lib/python2.6/dist-packages/binary-agilo-1.0_PRO_RC2-
> py2.6.egg/agilo/api/admin.py", line 49, in render_admin_panel
> return self.detail_save_view(req, cat, page, path_info)
> File "/usr/local/lib/python2.6/dist-packages/binary-agilo-1.0_PRO_RC2-
> py2.6.egg/agilo/scrum/team/admin.py", line 47, in detail_save_view
> return self.member_save(req, cat, page, name)
> File "/usr/local/lib/python2.6/dist-packages/binary-agilo-1.0_PRO_RC2-
> py2.6.egg/agilo/scrum/team/admin.py", line 154, in member_save
> team_member = self.tmm.get(name=req.args['team_member'])
> File "/usr/local/lib/python2.6/dist-packages/binary-agilo-1.0_PRO_RC2-
> py2.6.egg/agilo/core/model.py", line 962, in get
> m = self.get_cache().get(tuple(l))
> File "/usr/local/lib/python2.6/dist-packages/binary-agilo-1.0_PRO_RC2-
> py2.6.egg/agilo/api/model.py", line 117, in get
> return self._cache.get(self._get_cache_key(key_instance))
> File "/usr/local/lib/python2.6/dist-packages/binary-agilo-1.0_PRO_RC2-
> py2.6.egg/agilo/api/model.py", line 83, in _get_cache_key
> if self._cache.has_key(key_instance):
>
> I'm pretty sure the error here comes from a helper function mis-
> reading the kwargs from the post request, as when I examine the local
> variables at File "/usr/local/lib/python2.6/dist-packages/binary-
> agilo-1.0_PRO_RC2-py2.6.egg/agilo/core/model.py", line 962, in get I
> see this, which looks erroneous:
>
> kwargs={'name': [u'username', u'username']}
> l=[([u'username', u'username'],), ()]
> l_pk=([u'username', u'username'],)
I think this is what you already found out with python 2.6 and the
double parameters right?
What we could do is to rework out all the urls, and make sure they are
more REST, which is what we tried to do with Agilo 0.8, but there is
plenty of code to be migrated and checked ;-) Any help would be
greatly appreciated :-)
Best & Thanks for the feedback
ANdreaT
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
