When committing code you can mark ticket as completed, as well as have activeCollab connect specific commit with tickets, tasks, milestones etc that are mentioned in the comment. For example, if you commit a revision with following comment:
This commit completes Ticket #123
ticket will be completed automatically, Ticket #123 text will be converted to the link to that ticket, and system will record connection between the ticket and that revision.
Tracking time is not possible with commit comments at the moment, sorry.
Thank you for your interest in activeCollab. Please let us know if there's anything else that we can assist you with.
is there any documentation on how svn integration works? will be able to link svn repositories already on our server and assign say a specific tree to a project?
Yes, this module allows you to add Subversion repository to the project, but you'll need to use repository's root, not subfolder in the repository (this may not work as expected in all situations).
I also have a general query about SVN integration.
Can I use activeCollab on one server (main server), commit changes to another server (backup server), then if/when the main server is offline, use the backup server as the main server temporarily and commit changes to the main server when it is back online?
We're basically looking at the feasability of using activeCollab to organise our projects and files on a remote server, then using SVN as a method of synching/backing up that server data to a local in-house server as a temporary way to work with our activeCollab data until we could restore our main remote activeCollab server.
Other ideas and suggestions to acheive a similar redundancy would be appreciated, I just thought SVN could be a way to go about it, as (although we'd be looking at moving project data totalling about 8GB) we would be averaging about 100MB of new data per week.
Does the new module allow things like post commit hooks to add time and comment to the ticket?
Thanks