<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog - ShiftEleven &#187; issuetracker</title>
	<atom:link href="http://shifteleven.com/articles/tag/issuetracker/feed" rel="self" type="application/rss+xml" />
	<link>http://shifteleven.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 19 Sep 2009 11:19:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
		<item>
		<title>Issue Tracking + Git = ticgit</title>
		<link>http://shifteleven.com/articles/2008/05/10/issue-tracking-git-ticgit</link>
		<comments>http://shifteleven.com/articles/2008/05/10/issue-tracking-git-ticgit#comments</comments>
		<pubDate>Sun, 11 May 2008 00:08:53 +0000</pubDate>
		<dc:creator>K. Adam Christensen</dc:creator>
				<category><![CDATA[Version Control]]></category>
		<category><![CDATA[fork]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[issuetracker]]></category>
		<category><![CDATA[sinatra]]></category>
		<category><![CDATA[ticgit]]></category>
		<category><![CDATA[ticgit-watchtower]]></category>

		<guid isPermaLink="false">http://shifteleven.com/?p=73</guid>
		<description><![CDATA[So not only is git useful for the small projects it&#8217;s also good for keeping track of todos and issues.  Ticgit is a distributed ticketing systems based on git.   It provides a command line interface as well as a web interface via sinatra and stores all of the ticket info in a [...]]]></description>
			<content:encoded><![CDATA[<p>So not only is <a href="http://shifteleven.com/articles/2008/04/30/version-control-isnt-for-just-the-big-projects,">git useful for the small projects</a> it&#8217;s also good for keeping track of todos and issues.  <a href="http://github.com/schacon/ticgit">Ticgit</a> is a distributed ticketing systems based on git.   It provides a command line interface as well as a web interface via <a href="http://sinatrarb.com">sinatra</a> and stores all of the ticket info in a separate branch, called <code>ticgit</code>.  Rather clever I think.</p>
<p><span id="more-73"></span></p>
<p>Ticgit takes a simplistic approach to issue tracking as <a href="http://www.lighthouseapp.com">Lighthouse</a> has done.  You can comment, add tags, manage the state of an issue, save views, and change to whom an issue is assigned.  There is still more planned, like keeping track of milestones and syncing the tickets to Lighthouse.</p>
<p>As mentioned, there is a web interface to ticgit; however, it wasn&#8217;t my cup of tea.  So I have started my own web interface, <a href="http://github.com/pope/ticgit-watchtower.">tiwatchtower</a> It&#8217;s still a little rough around the edges, but I would love to hear any thoughts.</p>
<h3>Conclusion</h3>
<p>So far, I like it and it&#8217;s exciting to see how git can be pushed.  It&#8217;s great for keeping track of things that are on my mind without worrying about having to setup <a href="http://trac.edgewall.org/">trac</a> or having to use up a Lighthouse project.  It&#8217;s simple, effective, and worth a look at.</p>
]]></content:encoded>
			<wfw:commentRss>http://shifteleven.com/articles/2008/05/10/issue-tracking-git-ticgit/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>A Tip For People using Google Code and the Issue Tracker</title>
		<link>http://shifteleven.com/articles/2008/04/12/a-tip-for-people-using-google-code-and-the-issue-tracker</link>
		<comments>http://shifteleven.com/articles/2008/04/12/a-tip-for-people-using-google-code-and-the-issue-tracker#comments</comments>
		<pubDate>Sun, 13 Apr 2008 01:12:57 +0000</pubDate>
		<dc:creator>K. Adam Christensen</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[appengine]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[goole]]></category>
		<category><![CDATA[issuetracker]]></category>

		<guid isPermaLink="false">http://shifteleven.com/?p=49</guid>
		<description><![CDATA[If you are using Google Code, and let&#8217;s say that you want an issue addressed, like having ruby supported in GAE Please, Please, PLEASE, use the star voting and avoid making comments that are simply &#8220;+1&#8243;.  The more stars a defect has, the more attention it has, not the number of comments and especially [...]]]></description>
			<content:encoded><![CDATA[<p>If you are using Google Code, and let&#8217;s say that you want an issue addressed, like <a href="http://code.google.com/p/googleappengine/issues/detail?id=29.">having ruby supported in <acronym title="Google App Engine">GAE</acronym></a> Please, Please, PLEASE, use the star voting and avoid making comments that are simply &#8220;+1&#8243;.  The more stars a defect has, the more attention it has, not the number of comments and especially the number of &#8220;+1&#8243;s.</p>
<p>Actually, you <strong>hurt</strong> the initiative to get an issue addressed when you make those comments.  You see, when you star an issue, you receive emails when that issue gets updated or commented upon.  So if an issue has 100 or so &#8220;+1&#8243; comments, then whoever put a star on that defect is going to get 100 or so emails.  After getting 20 inane emails, one might decide to remove the star from the issue, thus lowering it&#8217;s rating and hurting the campaign.</p>
<p>So please, if you want to help, just star the issue.</p>
]]></content:encoded>
			<wfw:commentRss>http://shifteleven.com/articles/2008/04/12/a-tip-for-people-using-google-code-and-the-issue-tracker/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
