<?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: Basecamp as a bug-feature tracking system</title>
	<atom:link href="http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/</link>
	<description>Thoughts on building web apps, businesses, and virtual teams</description>
	<lastBuildDate>Thu, 09 Sep 2010 22:02:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Igor Balos</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-4833</link>
		<dc:creator>Igor Balos</dc:creator>
		<pubDate>Mon, 22 Mar 2010 09:58:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-4833</guid>
		<description>Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Viexhitiedtit</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-4832</link>
		<dc:creator>Viexhitiedtit</dc:creator>
		<pubDate>Sun, 21 Mar 2010 08:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-4832</guid>
		<description>i genuinely love your posting style, very useful.
don&#039;t quit as well as keep writing simply because it simply truly worth to read it,
impatient to look over alot more of your content pieces, good bye :)</description>
		<content:encoded><![CDATA[<p>i genuinely love your posting style, very useful.<br />
don&#8217;t quit as well as keep writing simply because it simply truly worth to read it,<br />
impatient to look over alot more of your content pieces, good bye :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ka Wai</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-3359</link>
		<dc:creator>Ka Wai</dc:creator>
		<pubDate>Mon, 22 Jun 2009 21:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-3359</guid>
		<description>Use DoneDone for bug tracking - simple, elegant: http://www.getdonedone.com - you can move companies and people from Basecamp, and you can download Bug Shooting on your desktop to upload screenshots to DoneDone.</description>
		<content:encoded><![CDATA[<p>Use DoneDone for bug tracking &#8211; simple, elegant: <a href="http://www.getdonedone.com" rel="nofollow">http://www.getdonedone.com</a> &#8211; you can move companies and people from Basecamp, and you can download Bug Shooting on your desktop to upload screenshots to DoneDone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Igor Balos</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-3214</link>
		<dc:creator>Igor Balos</dc:creator>
		<pubDate>Fri, 08 May 2009 08:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-3214</guid>
		<description>Hi Ivor, organizing tasks in basecamp can be messy. We tend to create todo lists which contain maximum 10-15 tasks, so it could be easier to review and organize tasks in them.

The problem with basecamp is that there are couple of missing features currently, which would make it a lot easier to use. 

For example:

	&lt;li&gt;move tasks/todo lists from one project to another&lt;/li&gt;

 	&lt;li&gt;select multiple tasks and move them to another todo list&lt;/li&gt;

 	&lt;li&gt;have a proper backlog, container in which you could put all the todo lists/tasks on which you would like to work in future (this would hide all task which don&#039;t have to be visible)&lt;/li&gt;



I hope some of these feature would be added in near future.</description>
		<content:encoded><![CDATA[<p>Hi Ivor, organizing tasks in basecamp can be messy. We tend to create todo lists which contain maximum 10-15 tasks, so it could be easier to review and organize tasks in them.</p>
<p>The problem with basecamp is that there are couple of missing features currently, which would make it a lot easier to use. </p>
<p>For example:</p>
<li>move tasks/todo lists from one project to another</li>
<li>select multiple tasks and move them to another todo list</li>
<li>have a proper backlog, container in which you could put all the todo lists/tasks on which you would like to work in future (this would hide all task which don&#8217;t have to be visible)</li>
<p>I hope some of these feature would be added in near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivor</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-3213</link>
		<dc:creator>Ivor</dc:creator>
		<pubDate>Thu, 07 May 2009 21:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-3213</guid>
		<description>Hi

I am using basecamp for project management. I have sprints as milestones and a &quot;Future Stories&quot; milestone where I through things that we will work on later (I just dont like the word backlog). 

My problem is that when I want to reorder tasks within a specific milestone. This is proving to be quite a chalance. When I view the ToDos I see all open todos which as you can imagine is quite a long list and reordering the items in the current milestone/sprint isnt working very well. Am I overlooking something obvious?</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>I am using basecamp for project management. I have sprints as milestones and a &#8220;Future Stories&#8221; milestone where I through things that we will work on later (I just dont like the word backlog). </p>
<p>My problem is that when I want to reorder tasks within a specific milestone. This is proving to be quite a chalance. When I view the ToDos I see all open todos which as you can imagine is quite a long list and reordering the items in the current milestone/sprint isnt working very well. Am I overlooking something obvious?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scrum in virtual teams &#124; Wildbit</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2733</link>
		<dc:creator>Scrum in virtual teams &#124; Wildbit</dc:creator>
		<pubDate>Thu, 04 Dec 2008 17:20:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2733</guid>
		<description>[...] communicate in three ways: Campfire, Basecamp and IM. For scrum we use Campfire.  Campfire is a place where we have 10AM meetings and hang [...]</description>
		<content:encoded><![CDATA[<p>[...] communicate in three ways: Campfire, Basecamp and IM. For scrum we use Campfire.  Campfire is a place where we have 10AM meetings and hang [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sal</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2593</link>
		<dc:creator>Sal</dc:creator>
		<pubDate>Sun, 09 Nov 2008 10:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2593</guid>
		<description>You should also check out DeskAway. Its project management with issue tracking built in. So you can assign an Issue, a team member can &quot;Accept&quot; it and then mark it complete when its done.</description>
		<content:encoded><![CDATA[<p>You should also check out DeskAway. Its project management with issue tracking built in. So you can assign an Issue, a team member can &#8220;Accept&#8221; it and then mark it complete when its done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Igor Balos</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2571</link>
		<dc:creator>Igor Balos</dc:creator>
		<pubDate>Tue, 04 Nov 2008 18:10:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2571</guid>
		<description>Jade, 

as for the screenshot tool, I prefer snagit :) , unfortunately no screenshot tool in basecamp</description>
		<content:encoded><![CDATA[<p>Jade, </p>
<p>as for the screenshot tool, I prefer snagit :) , unfortunately no screenshot tool in basecamp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Nagele</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2569</link>
		<dc:creator>Chris Nagele</dc:creator>
		<pubDate>Tue, 04 Nov 2008 17:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2569</guid>
		<description>Jade,

That is one thing we definitely miss, but we are working on something that will work with Basecamp to-do which might help. Stay tuned.</description>
		<content:encoded><![CDATA[<p>Jade,</p>
<p>That is one thing we definitely miss, but we are working on something that will work with Basecamp to-do which might help. Stay tuned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jade</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2563</link>
		<dc:creator>Jade</dc:creator>
		<pubDate>Tue, 04 Nov 2008 15:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2563</guid>
		<description>How about SVN links? What do you enter when doing a commit to link to a to-do list? Are there any links the other way?

What about the FogBugz feature that has been huge for us, the screenshot tool. Is there something like that in Basecamp.

Thanks for sharing your experience.</description>
		<content:encoded><![CDATA[<p>How about SVN links? What do you enter when doing a commit to link to a to-do list? Are there any links the other way?</p>
<p>What about the FogBugz feature that has been huge for us, the screenshot tool. Is there something like that in Basecamp.</p>
<p>Thanks for sharing your experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Nagele</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2557</link>
		<dc:creator>Chris Nagele</dc:creator>
		<pubDate>Tue, 04 Nov 2008 01:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2557</guid>
		<description>Hi Jade, yes. We decided not to use FogBugz anymore for task management. However, we still use it for support requests.</description>
		<content:encoded><![CDATA[<p>Hi Jade, yes. We decided not to use FogBugz anymore for task management. However, we still use it for support requests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jade</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2555</link>
		<dc:creator>Jade</dc:creator>
		<pubDate>Mon, 03 Nov 2008 22:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2555</guid>
		<description>So is FogBugz out?</description>
		<content:encoded><![CDATA[<p>So is FogBugz out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simonhamp</title>
		<link>http://wildbit.com/blog/2008/11/03/basecamp-as-a-bug-feature-tracking-system/comment-page-1/#comment-2554</link>
		<dc:creator>simonhamp</dc:creator>
		<pubDate>Mon, 03 Nov 2008 19:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildbit.com/?p=276#comment-2554</guid>
		<description>I was doing this for a project a while back. It was great, but the client didn&#039;t &#039;get it&#039;... I think training the client is an important step that mustn&#039;t be overlooked. But it is definitely worth the effort.. as you say, they feel more involved, and it adds greatly to the process.</description>
		<content:encoded><![CDATA[<p>I was doing this for a project a while back. It was great, but the client didn&#8217;t &#8216;get it&#8217;&#8230; I think training the client is an important step that mustn&#8217;t be overlooked. But it is definitely worth the effort.. as you say, they feel more involved, and it adds greatly to the process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
