<?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: Help Desk Contenders: First Looks &#8211; open source</title>
	<atom:link href="http://blogs.backupbrain.com.au/glenn/2006/02/13/help-desk-contenders-first-looks-open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.backupbrain.com.au/glenn/2006/02/13/help-desk-contenders-first-looks-open-source/</link>
	<description></description>
	<lastBuildDate>Mon, 16 Oct 2006 21:09:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: kato</title>
		<link>http://blogs.backupbrain.com.au/glenn/2006/02/13/help-desk-contenders-first-looks-open-source/comment-page-1/#comment-21</link>
		<dc:creator>kato</dc:creator>
		<pubDate>Fri, 21 Apr 2006 18:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.backupbrain.com.au/glenn/2006/02/13/help-desk-contenders-first-looks-open-source/#comment-21</guid>
		<description>Zentrack is not a xoops module, nor is the xoops module an official port from the ZT team.  It is a fully standalone application.

It is intended, to confirm your assumption, designed more readily for internal use as a help desk system or trouble ticket tool rather than a customer oriented tool.

The UI has been updated in recent versions (since your review) to allow for more advanced customizations.  Adding/removing tabs, features, etc, was one of the feature requests that was addressed.

Best</description>
		<content:encoded><![CDATA[<p>Zentrack is not a xoops module, nor is the xoops module an official port from the ZT team.  It is a fully standalone application.</p>
<p>It is intended, to confirm your assumption, designed more readily for internal use as a help desk system or trouble ticket tool rather than a customer oriented tool.</p>
<p>The UI has been updated in recent versions (since your review) to allow for more advanced customizations.  Adding/removing tabs, features, etc, was one of the feature requests that was addressed.</p>
<p>Best</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BackupBrain: My MicroISV Venture &#187; Blog Archive &#187; Help desk contenders: First Looks - commercial contenders</title>
		<link>http://blogs.backupbrain.com.au/glenn/2006/02/13/help-desk-contenders-first-looks-open-source/comment-page-1/#comment-20</link>
		<dc:creator>BackupBrain: My MicroISV Venture &#187; Blog Archive &#187; Help desk contenders: First Looks - commercial contenders</dc:creator>
		<pubDate>Fri, 24 Feb 2006 03:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.backupbrain.com.au/glenn/2006/02/13/help-desk-contenders-first-looks-open-source/#comment-20</guid>
		<description>[...] That quote reminds me of BugZilla, whose interface was the main reason that I was turned off using it. &#8220;Help desk software is intrinsically a &#8216;high read&#8217; environment. Thereâ€™s simply alot of information that needs to be consumed by staff members &#8230;. An effective approach is to use colors and images to give a quick understanding of the situation.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] That quote reminds me of BugZilla, whose interface was the main reason that I was turned off using it. &#8220;Help desk software is intrinsically a &#8216;high read&#8217; environment. Thereâ€™s simply alot of information that needs to be consumed by staff members &#8230;. An effective approach is to use colors and images to give a quick understanding of the situation.&#8221; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
