<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Axosoft OnTime to Subversion (SVN) hooks via TortoiseSVN</title>
	<atom:link href="http://www.webapper.com/blog/index.php/2009/03/26/axosoft-ontime-to-subversion-svn-hooks-via-tortoisesvn/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webapper.com/blog/index.php/2009/03/26/axosoft-ontime-to-subversion-svn-hooks-via-tortoisesvn/</link>
	<description>Web Application Engineers</description>
	<lastBuildDate>Mon, 05 Dec 2011 17:24:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nat Papovich</title>
		<link>http://www.webapper.com/blog/index.php/2009/03/26/axosoft-ontime-to-subversion-svn-hooks-via-tortoisesvn/comment-page-1/#comment-6241</link>
		<dc:creator>Nat Papovich</dc:creator>
		<pubDate>Fri, 10 Jul 2009 16:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.webapper.com/blog/?p=997#comment-6241</guid>
		<description>Scott - yes FogBugz has a much smaller featureset than OnTime. And we actually used many of those features in OnTime like workflow-specific templates, the client portal, and customizable workflows. We switched mainly to give FogBugz a try, and it suits us well enough. Not perfectly, but then neither did OnTime. Ultimately, we&#039;d like to -gasp- build our own, but we haven&#039;t done it yet. For a company like ours, task and ticket management can be a strategic advantage.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; yes FogBugz has a much smaller featureset than OnTime. And we actually used many of those features in OnTime like workflow-specific templates, the client portal, and customizable workflows. We switched mainly to give FogBugz a try, and it suits us well enough. Not perfectly, but then neither did OnTime. Ultimately, we&#8217;d like to -gasp- build our own, but we haven&#8217;t done it yet. For a company like ours, task and ticket management can be a strategic advantage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Vickery</title>
		<link>http://www.webapper.com/blog/index.php/2009/03/26/axosoft-ontime-to-subversion-svn-hooks-via-tortoisesvn/comment-page-1/#comment-5433</link>
		<dc:creator>Scott Vickery</dc:creator>
		<pubDate>Wed, 24 Jun 2009 18:31:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.webapper.com/blog/?p=997#comment-5433</guid>
		<description>Out of curiosity, why did you switch from OnTime to FogBugz?  FogBugz seems to lack a lot of functionality in comparison to OnTime.</description>
		<content:encoded><![CDATA[<p>Out of curiosity, why did you switch from OnTime to FogBugz?  FogBugz seems to lack a lot of functionality in comparison to OnTime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Behrens</title>
		<link>http://www.webapper.com/blog/index.php/2009/03/26/axosoft-ontime-to-subversion-svn-hooks-via-tortoisesvn/comment-page-1/#comment-2084</link>
		<dc:creator>Brandon Behrens</dc:creator>
		<pubDate>Tue, 21 Apr 2009 23:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.webapper.com/blog/?p=997#comment-2084</guid>
		<description>I think you can get around hacking the primary keys by a simple naming convention.  Prefix defects with d, features with f, tasks with t etc.  Then in the TortoiseLinker.asp file, check the first character to find out where to redirect the user to, instead of basing it on the defect id in the querystring.  

While this feels kind of dirty to me as well, it&#039;s preferrable to modifying the ontime database primary key and potentially voiding my support contract.  

Your post was extremely helpful, Thanks.</description>
		<content:encoded><![CDATA[<p>I think you can get around hacking the primary keys by a simple naming convention.  Prefix defects with d, features with f, tasks with t etc.  Then in the TortoiseLinker.asp file, check the first character to find out where to redirect the user to, instead of basing it on the defect id in the querystring.  </p>
<p>While this feels kind of dirty to me as well, it&#8217;s preferrable to modifying the ontime database primary key and potentially voiding my support contract.  </p>
<p>Your post was extremely helpful, Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

