Hi Martin, thanks for your reply and I'm really sorry for the late reply but I could not manage it to look into the commit stuff until tonight.
Well, I already started to write you an e-mail 2 hours ago but then I started again to investigate on this stuff. However, it seems I found a solution that works now and here it is: We did not use the Agilo hooks but instead the standard trac hook ... more precisely old trac hooks and I'm assuming with the upgrade to 0.12.1 we broke the "put a commit message into the history of the referenced ticket" functionality because obviously there have not been any commit messages in the last couple of days :-/ Nevertheless, I lookup up the "current" (5 months old) version of the post-commit-hook suggested for trac and tried this one - you can find it at http://trac.edgewall.org/browser/trunk/contrib/trac-svn-hook . Guess what: It works again! Yeah! Does the Agilo hooks give me any significant advantages expect some permissions stuff on committing to tickets? Cheers Andreas On 15 Feb., 11:10, Martin Häcker <[email protected]> wrote: > Hi Andreas, > > Am 14.02.11 18:10, schrieb andrgrau: > > > since we have been using Agilo for the last 3 weeks we encountered > > some "issues" with SVN/Subversion integration. However, I'm not so > > into the whole Python stuff and the scripts so I just want to ask > > first - I hope no one is blaming me for this ;-) > > > We're using trac/Agilo not only for pure Scrum development but also > > for some support tasks which come in on a daily basis and need to be > > done. However, these Support tickets (a new ticket type) are not > > configured to be in a sprint but they sometimes involve code changes > > which I want to be shown in the history of this ticket. > > > But currently, Agilo does not show me the commits of such tickets in > > the ticket history. This only happens if tickets are assigned to the > > current sprint. > > So, you see the commit in the timeline and it has the right syntax, but > the ticket is not changed to include a link to that commit - right? > > > Any idea how to solve this? (I know, just look into the > > post_commit_hook but Python is not my language so I decided to ask > > first.) > > I'm surprised by this behaviour as for the commit hook it should not > matter whether a ticket is in a sprint or not - all it (should) need is > the correct ticket id. Can you describe your setup in more detail and > how to reproduce this behaviour? > > I'd probably need the config file (maybe off list to > <[email protected]>) and a detailed description of what steps > you took to show the problem. > > Thanks in advance! > > Martin -- 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
