<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.dotnetzone.gr:443/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Comparison of issue tracking systems </title><link>https://www.dotnetzone.gr:443/cs/blogs/papadi/archive/2010/02/19/comparison-of-issue-tracking-systems.aspx</link><description>Couple of years ago Sotiris Fillippidis - friend of mine and author of famous Zaharias Dentoftiahno tales - initiated a table of existing issue tracking systems to compare their features. Here is his blog post . Today I came accross something similar</description><dc:language>el</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator><item><title>re: Comparison of issue tracking systems </title><link>https://www.dotnetzone.gr:443/cs/blogs/papadi/archive/2010/02/19/comparison-of-issue-tracking-systems.aspx#57217</link><pubDate>Sat, 20 Feb 2010 18:32:21 GMT</pubDate><guid isPermaLink="false">2622095e-976c-431a-859e-16783ec7ecd7:57217</guid><dc:creator>napoleon</dc:creator><description>&lt;p&gt;Very good summary, useful for teams&lt;/p&gt;
</description></item></channel></rss>